All About FNDCPASS

To change Apps Password

FNDCPASS apps/ 0 Y system/ SYSTEM APPLSYS 

Syntax:

FNDCPASS apps/apps  0 Y system/manager SYSTEM APPLSYS <Password>

Ex :

FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS APPSPWD

To change an application schema password

Syntax:
FNDCPASS apps/apps  0 Y system/manager ORACLE  <Schema Name> <Schema Password> 

EX :

FNDCPASS apps/apps 0 Y system/manager ORACLE GL GLPWD

To change all application schema passwords at once.

This feature is available from 11i.ATG_PF.H Rollup 3.

Syntax :

FNDCPASS apps/ 0 Y system/ ALLORACLE <Schema Password>

Ex :

FNDCPASS apps/apps123 0 Y system/manager123 ALLORACLE schemapass123

To change an Application User (EBS Fornt – End) Password

Syntax :

FNDCPASS apps/apps 0 Y system/manager USER <Password>

Ex :
FNDCPASS apps/apps 0 Y system/manager USER ADITHIYAN ORACLEAPPSDBA

Please note that when we changing the apps password it is very important to run autoconfig to make the changes in across all the application or you will need change the apps password in following files manually if it exists.

 $IAS_ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app
 $FND_TOP/resource/wfmail.cfg
 $COMMON_TOP/admin/scripts/adcmctl.ch
 $OA_HTML/bin/appsweb.cfg
 $AD_TOP/admin/template/CGIcmd.dat


Changing Password Using Query

Note : It is not Recommended

begin
if fnd_user_pkg.changepassword('RAJSHEKHAR','welcome@123') then
null;

end if;
end;

Enable User

begin
exec fnd_user_pkg.enableuser('RAJSHEKHAR',sysdate,sysdate+1000) then
commit;

end;

DBNEWID Utility

DBNEWID is a database utility that can change the internal database identifier (DBID) and the database name (DBNAME) for an operational database.

This chapter contains the following sections:

   What Is the DBNEWID Utility?

Prior to the introduction of the DBNEWID utility, you could manually create a copy of a database and give it a new database name (DBNAME) by re-creating the control file. However, you could not give the database a new identifier (DBID). The DBID is an internal, unique identifier for a database. Because Recovery Manager (RMAN) distinguishes databases by DBID, you could not register a seed database and a manually copied database together in the same RMAN repository. The DBNEWID utility solves this problem by allowing you to change any of the following:

• Only the DBID of a database
• Only the DBNAME of a database
• Both the DBNAME and DBID of a database

Changing the DBID and DBNAME of a Database

This section contains these topics:

• Changing the DBID and Database Name
• Changing Only the Database Name
• Troubleshooting a DBID Change Operation
• Troubleshooting a Database Name Change Operation

Changing the DBID and Database Name

The following steps describe how to change the DBID of a database. Optionally, you can change the database name as well.

1. Ensure that you have a recoverable whole database backup.
2. Ensure that the target database is mounted but not open, and that it was shut down consistently prior to mounting. For example:

   SHUTDOWN IMMEDIATE
   STARTUP MOUNT
   
   

3. Invoke the DBNEWID utility on the command line, specifying a valid user with the SYSDBA privilege. For example:

   % nid TARGET=SYS/oracle@test_db
   
   

   To change the database name in addition to the DBID, specify the DBNAME parameter. This example changes the name to test_db2:

   % nid TARGET=SYS/oracle@test DBNAME=test_db2
   
   

   The DBNEWID utility performs validations in the headers of the datafiles and control files before attempting I/O to the files. If validation is successful, then DBNEWID prompts you to confirm the operation (unless you specify a log file, in which case it does not prompt), changes the DBID for each datafile (including offline normal and read-only datafiles), and then exits. The database is left mounted but is not yet usable. For example:

   DBNEWID: Release 9.2.0.1.0
   
   (c) Copyright 2002 Oracle Corporation.  All rights reserved.
   
   Connected to database TEST_DB (DBID=3942195360)
   
   Control Files in database:
       /oracle/dbs/cf1.f
       /oracle/dbs/cf2.f
   
   Change database id of database SOLARIS? (Y/[N]) => y
   
   Proceeding with operation
       Datafile /oracle/dbs/tbs_01.f - changed
       Datafile /oracle/dbs/tbs_02.f - changed
       Datafile /oracle/dbs/tbs_11.f - changed
       Datafile /oracle/dbs/tbs_12.f - changed
       Datafile /oracle/dbs/tbs_21.f - changed
   
   New DBID for database TEST_DB is 3942196782.
   All previous backups and archived redo logs for this database are unusable
   Proceed to shutdown database and open with RESETLOGS option.
   DBNEWID - Database changed.
   
   

   If validation is not successful, then DBNEWID terminates and leaves the target database intact. You can open the database, fix the error, and then either resume the DBNEWID operation or continue using the database without changing its DBID.
4. After DBNEWID successfully changes the DBID, shut down the database:

   SHUTDOWN IMMEDIATE
   
   

5. Mount the database. For example:

   STARTUP MOUNT
   
   

6. Open the database in RESETLOGS mode and resume normal use. For example:

   ALTER DATABASE OPEN RESETLOGS;
   
   

   Make a new database backup. Because you reset the online redo logs, the old backups and archived logs are no longer usable in the current incarnation of the database.

Changing Only the Database Name

The following steps describe how to change the database name without changing the DBID.

1. Ensure that you have a recoverable whole database backup.
2. Ensure that the target database is mounted but not open, and that it was shut down consistently prior to mounting. For example:

   SHUTDOWN IMMEDIATE
   STARTUP MOUNT
   
   

3. Invoke the utility on the command line, specifying a valid user with the SYSDBA privilege. You must specify both the DBNAME and SETNAME parameters. This example changes the name to test_db2:

   % nid TARGET=SYS/oracle@test_db DBNAME=test_db2 SETNAME=YES
   
   

   DBNEWID performs validations in the headers of the control files (not the datafiles) before attempting I/O to the files. If validation is successful, then DBNEWID prompts for confirmation, changes the database name in the control files, and exits. After DBNEWID completes successfully, the database is left mounted but is not yet usable.

   DBNEWID: Release 9.2.0.1.0
   
   (c) Copyright 2002 Oracle Corporation.  All rights reserved.
   
   
   Connected to database TEST_DB (DBID=3942196782)
   
   Control Files in database:
       /oracle/dbs/cf1.f
       /oracle/dbs/cf2.f
   
   Change database name of database TEST_DB to TEST_DB2? (Y/[N]) => Y
   
   Proceeding with operation
   
   Database name changed from TEST_DB to TEST_DB2 - database needs to be 
   shutdown.
   Modify parameter file and generate a new password file before restarting.
   
   DBNEWID - Successfully changed database name
   
   

   If validation is not successful, then DBNEWID terminates and leaves the target database intact. You can open the database, fix the error, and then either resume the DBNEWID operation or continue using the database without changing the database name.
4. Shut down the database. For example:

   SHUTDOWN IMMEDIATE
   
   

5. Set the DB_NAME initialization parameter in the initialization parameter file to the new database name.
6. Create a new password file.
7. Start up the database and resume normal use. For example:

   STARTUP

Migrating Oracle E­-Business Suite R12 from Linux  32­bit to Linux 64-bit

  

Prerequisites

Step :1

Shut down the application tier services

Step 2:

Perform all prerequisite steps in the Rapid Clone document

Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.1]

Prerequisite Tasks:

1.Run AutoConfig on the application tiers

2.Synchronize appsutil on the database tier nodes

Run admkappsutil.pl

3.Run AutoConfig on the database tier

4.Run Maintain Snapshot Information

Log in to each application tier node as the APPLMGR user, and run "Maintain Snapshot Information" in AD Administration. To update the snapshot, please select the following options "Update Current View Snapshot" and "Update Complete APPL_TOP".

Step 3:

Install the 64­Bit Database Oracle home in Target Node:

On the target Linux 64­bit machine, perform the installation of the database that corresponds to the database version on the source system.

 Migration Process

Migrate the Database Tier

1.Shut down the application tier services

2.Export OLAP analytical workspaces (conditional)

To migrate from a 32bit installation to a 64bit installation of Oracle OLAP, the basic steps are:

1) On the original 32­bit installation, export user created AWs and then delete these AWs.

2) Remove OLAP from the 32bit installation using the Oracle Universal Installer.

3) For the new 64­bit installation make certain Oracle OLAP is installed.

4) Restore OLAP to the migrated database.

5) Import all AWs from the 32bit installation.

1.Create the RDBMS ORACLE_HOME on the target machine(Install 11GR2 Home) Install 11R2 Software at target System

Apply all the pre­req Additional patches suggested in Doc:[ID 1058763.1]

Export OLAP analytical workspaces in source database Tier

Detailed steps:

1.  To obtain the list of AWs that need to be exported execute this command and then proceed to export the AWs that are NOT owned by 0:

select OWNER, AW_NAME ,PAGESPACES from dba_aws where owner!='SYS'; The columns 'OWNER' and 'AW_NAME' will be needed in the further steps.

The 'pagespaces' give you a rough indication of the size of an AW. This way  you get a

general idea

about which are the largest AW's that will take the longest to export.

The AW's belonging to SYS are not included as they are re­created when OLAP is installed.

So there is no need to export them.

2.  Use the following SQL commands, for each AW that was identified in step #1 (NOTE:

All quotes are single quotes):

­­­ Replace OWNER.AW_NAME with the the actual OWNER.AW_NAME name

SQL> exec dbms_aw.execute('aw attach OWNER.AW_NAME rw');

­­ (NOTE: this following statement is critical so everything in the AW is in STATUS) SQL> exec dbms_aw.execute('allstat');

­­­ Replace ALIAS_DIR with a defined directory alias

­­­ Replace export_file_name.eif with a valid eif file name

SQL> exec dbms_aw.execute('export all to eif file ''ALIAS_DIR/export_file_name.eif  ''');

­­­ Replace OWNER.AW_NAME with the actual OWNER.AW_NAME name

SQL> exec dbms_aw.execute('aw detach OWNER.AW_NAME'); If  you get the following error:

ERROR at line 1:

ORA­33390: There are no objects to export. ORA­06512: at "SYS.DBMS_AW", line 93

ORA­06512: at "SYS.DBMS_AW", line 122

ORA­06512: at line 1

SQL>

It means the AW is empty and there is nothing to export. You can safely delete the AW.

Export all the AW’s from database to EIF file for each schemas

SQL> conn apps/test1234

Connected.

SQL> create directory expaw as '/d02/PROD_TEST/aw'; Directory created.

SQL>conn sys as sysdba

SQL>grant read,write on directory expaw to apps; SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 ­ Pr oduction

With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@erpr12 11.2.0]$ mkdir /d02/PROD_TEST/aw

[oracle@erpr12 11.2.0]$ cd /d02/PROD_TEST/aw

[oracle@erpr12 aw]$ ls

[oracle@erpr12 aw]$ pwd

/d02/PROD_TEST/aw

[oracle@erpr12 aw]$ cd ­

/d02/PROD_TEST/db/tech_st/11.2.0

Connect as Apps Schema

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 ­ Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> col owner format a15 col aw_name format a15

select OWNER, AW_NAME ,PAGESPACES from dba_aws

where owner != 'SYS' order by 1,2;SQL> SQL> SQL> SQL>   2  SQL> SP2­0734: unknown command beginning "where owne..." ­ rest of line ignored.

SQL> select OWNER, AW_NAME ,PAGESPACES from dba_aws where owner != 'SYS' order b y 1,2;

OWNER           AW_NAME        PAGESPACES

­­­­­­­­­­­­­­­ ­­­­­­­­­­­­­­­ ­­­­­­­­­­

APPS	ODPCODE	1107
APPS	XWDEVKIT	1082
FPA	FPAPJP	504
ZPB	ZPBANNOT	7
ZPB	ZPBCODE	458
ZPB	ZPBDATA	7

6 rows selected.

SQL> exec dbms_aw.execute('aw attach apps.ODPCODE rw'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('allstat'); PL/SQL procedure successfully completed. SQL> exec dbms_aw.execute('allstat');

SQL> exec dbms_aw.execute('export all to eif file ''expaw/appsaw1.eif'''); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('aw detach apps.ODPCODE');

Commit complete.

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 ­ Pr oduction

With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@erpr12 11.2.0]$ cd /d02/

lost+found/ Patches/ PROD_TEST/  tmp_test/ [oracle@erpr12 11.2.0]$ cd /d02/PROD_TEST/aw [oracle@erpr12 aw]$ vi appsaw1.eif [oracle@erpr12 aw]$

APPS	ODPCODE	1107
APPS	XWDEVKIT	1082
FPA	FPAPJP	504
ZPB	ZPBANNOT	7
ZPB	ZPBCODE	458
ZPB	ZPBDATA	7

Schema  :APPS

Objects   :ODPCODE

SQL> exec dbms_aw.execute('aw attach apps.ODPCODE rw'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('allstat'); PL/SQL procedure successfully completed. SQL> exec dbms_aw.execute('allstat'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('export all to eif file ''expaw/appsaw1.eif'''); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('aw detach apps.ODPCODE');

Schema   :APPS 

Object       :XWDEVKIT

exec dbms_aw.execute('aw attach apps.XWDEVKIT rw');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('export all to eif file ''expaw/XWDEVKIT1.eif''');

exec dbms_aw.execute('aw detach apps.XWDEVKIT');

commit;

Schema     :FPA 

Object        :FPAPJP

exec dbms_aw.execute('aw attach FPA.FPAPJP rw');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('export all to eif file ''expaw/FPAPJP1.eif''');

exec dbms_aw.execute('aw detach FPA.FPAPJP');

commit;

Schema   :ZPB

Object       : ZPBANNOT

exec dbms_aw.execute('aw attach ZPB.ZPBANNOT rw');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('export all to eif file ''expaw/ZPBANNOT1.eif''');

exec dbms_aw.execute('aw detach ZPB.ZPBANNOT');

commit;

Schema   :ZPB

Object       :ZPBCODE

exec dbms_aw.execute('aw attach ZPB.ZPBCODE rw');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('export all to eif file ''expaw/ZPBCODE1.eif''');

exec dbms_aw.execute('aw detach ZPB.ZPBCODE');

commit;

Schema     :ZPB Object        :ZPBDATA

exec dbms_aw.execute('aw attach ZPB.ZPBDATA rw');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('allstat');

exec dbms_aw.execute('export all to eif file ''expaw/ZPBDATA1.eif''');

exec dbms_aw.execute('aw detach ZPB.ZPBDATA');

commit;

  

Removing the AW’s from the Source Database

3.  Delete each AW that has been exported in step #2, using the SQL command:

­­­ Replace OWNER.AW_NAME with the actual OWNER.AW_NAME name

SQL> exec dbms_aw.execute('aw delete OWNER.AW_NAME');

exec dbms_aw.execute('aw delete APPS.ODPCODE'); exec dbms_aw.execute('aw delete APPS.XWDEVKIT'); exec dbms_aw.execute('aw delete FPA.FPAPJP');

exec dbms_aw.execute('aw delete ZPB.ZPBANNOT');

exec dbms_aw.execute('aw delete ZPB.ZPBCODE');

exec dbms_aw.execute('aw delete ZPB.ZPBDATA');

APPS	ODPCODE	1107
APPS	XWDEVKIT	1082
FPA	FPAPJP	504
ZPB	ZPBANNOT	7
ZPB	ZPBCODE	458
ZPB	ZPBDATA	7

4.  Remove OLAP from the 32bit database and cleanup any INVALID OLAP related objects by executing the following commands:

$ cd $ORACLE_HOME/olap/admin ­­­>>> required to locate all embedded calls to other scripts

$ sqlplus /nolog

> conn / as sysdba

SQL> @?/olap/admin/catnoamd.sql SQL> @?/olap/admin/olapidrp.plb SQL> @?/olap/admin/catnoaps.sql SQL> @?/olap/admin/catnoxoq.sql SQL> @?/rdbms/admin/utlrp.sql

SQL> select owner, object_name, object_type from dba_objects where status <> 'VALID';

Remove any INVALID OLAP related objects drop function sys.OLAPIHANDSHAKE

drop public synonym OLAPIBOOTSTRAP

drop public synonym OLAPIHANDSHAKE

drop package sys.GENINTERRUPTABLEINTERFACE SQL> drop function sys.OLAPIBOOTSTRAP;

Function dropped.

SQL> drop function sys.OLAPIHANDSHAKE; Function dropped.

SQL> drop package sys.GENINTERRUPTABLEINTERFACE; Package dropped.

Create a .trc file to use as template to re­create the control files on the target machine.

Run the following command on the source database to create a .trc file, which you will use to recreate the control files on the target machine in a later step.

$ sqlplus /nolog

SQL> connect / as sysdba

SQL> alter database backup controlfile to trace

Shut down the original (source) database.

Perform a SHUTDOWN NORMAL on the source database, and stop the database listener.

Migrate Linux 32­bit database to Linux x86­64

1.Copy the database (.dbf) files from the source machine to the target machine

2.Copy the database configuration files init.ora and ifilecbo.ora

3.Modify configuration files on target machine to reflect the new environment. Also, set

_system_trig_enabled=false

4.Start up the database in nomount mode

5.Recreate the database using backup control files(Restlog mode)

Start the database in upgrade mode startup upgrade

6.Run $ORACLE_HOME/rdbms/admin/utlirp.sql to invalidate the PL/SQL modules

7.Install OLAP

Add OLAP back into the database by connecting to the database '/ as sysdba' and executing: SQL> @?/olap/admin/olap.sql SYSAUX TEMP;

8.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.

SQL>@?/rdbms/admin/utlrp.sql

9. Use the following SQL commands to import each of the exported AWs.  NOTE: All quotes are single quotes and make sure that you use the right combination of EIF file and OWNER.AW_NAME

SQL > exec dbms_aw.execute('aw create OWNER.AW_NAME');

­­­ Replace ALIAS_DIR with a defined directory alias

SQL> exec dbms_aw.execute('import all from eif file ''ALIAS_DIR/export_file_name.eif''  data dfns');

SQL> exec dbms_aw.execute('update'); SQL> commit;

­­­ Replace OWNER.AWNAME with the actual OWNER.AW_NAME name

SQL> exec dbms_aw.execute('aw detach OWNER.AW_NAME);

Import AW’s to Target Instance

Connect as apps user

SQL> create directory expaw as '/oracle/AWS_EXP'; Directory created.

SQL> grant read,write on directory expaw to apps; Grant succeeded.

SQL> grant read,write on directory expaw to FPA; Grant succeeded.

SQL> grant read,write on directory expaw to ZPB; Grant succeeded.

SQL> conn apps/march08

Connected.

SQL> grant read,write on directory expaw to FPA; Grant succeeded.

SQL> grant read,write on directory expaw to ZPB; Grant succeeded.

SQL> exec dbms_aw.execute('aw create APPS.ODPCODE'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('import all from eif file ''expaw/appsaw1.eif'' data dfns') PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('update'); PL/SQL procedure successfully completed.

 SQL> commit; Commit complete.

SQL> exec dbms_aw.execute('aw detach  APPS.ODPCODE'); PL/SQL procedure successfully completed.

SQL> exit

SQL> exec dbms_aw.execute('aw create APPS.XWDEVKIT'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('import all from eif file ''expaw/XWDEVKIT1.eif'' data dfns')

PL/SQL procedure successfully completed. SQL> exec dbms_aw.execute('update'); PL/SQL procedure successfully completed. SQL> commit;

Commit complete.

SQL> exec dbms_aw.execute('aw detach  APPS.XWDEVKIT'); PL/SQL procedure successfully completed.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 ­ 64 bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@dev 11.2.0]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Wed Mar 27 22:54:44 2013

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 ­ 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> exec dbms_aw.execute('aw create FPA.FPAPJP'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('import all from eif file ''expaw/FPAPJP1.eif''data dfns');

PL/SQL procedure successfully completed. SQL> exec dbms_aw.execute('update'); PL/SQL procedure successfully completed. SQL> commit;

Commit complete.

SQL> exec dbms_aw.execute('aw detach  FPA.FPAPJP'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('aw create ZPB.ZPBANNOT'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('update'); PL/SQL procedure successfully completed. SQL> commit;

Commit complete.

SQL> exec dbms_aw.execute('aw detach ZPB.ZPBANNOT'); PL/SQL procedure successfully completed.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 ­ 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>  exec dbms_aw.execute('aw create ZPB.ZPBCODE');

PL/SQL procedure successfully completed.

SQL>  exec dbms_aw.execute('import all from eif file ''expaw/ZPBCODE1.eif'' data dfns'); PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('update'); PL/SQL procedure successfully completed. SQL>  commit;

Commit complete.

SQL> exec dbms_aw.execute('aw detach ZPB.ZPBCODE'); PL/SQL procedure successfully completed.

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 ­ 64bit

Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@dev 11.2.0]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Wed Mar 27 23:49:26 2013

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 ­ 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> ZPBDATA

SP2­0042: unknown command "ZPBDATA" ­ rest of line ignored. SQL> exec dbms_aw.execute('aw create ZPB.ZPBDATA');

PL/SQL procedure successfully completed.

SQL> exec dbms_aw.execute('import all from eif file ''expaw/zpbaw2.eif'' data dfns'); BEGIN dbms_aw.execute('import all from eif file ''expaw/zpbaw2.eif'' data dfns'); END;

*

ERROR at line 1:

ORA­36786: File EXPAW/zpbaw2.eif does not exist or cannot be accessed. ORA­27300: OS system dependent operation:open failed failed with status: 2

ORA­27301: OS failure message: No such file or directory

ORA­27302: failure occurred at: SlfFopen1

ORA­06512: at "SYS.DBMS_AW", line 93

ORA­06512: at "SYS.DBMS_AW", line 122

ORA­06512: at line 1

SQL> exec dbms_aw.execute('update'); PL/SQL procedure successfully completed. SQL> commit;

Commit complete.

SQL> exec dbms_aw.execute('aw detach ZPB.ZPBDATA'); PL/SQL procedure successfully completed.

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 i

re­create the java system in New Configured Oracle Home

If the JServer JAVA Virtual Machine component is installed, perform the following steps

After connecting as SYS:

ORA­29516: AURORA ASSERTION FAILURE: CREATE OR REPLACE JAVA [ID 415780.1]

10.Remove _system_trig_enabled=false from init.ora

11.Shutdown and restart the database normally

Post­Migration Tasks

Please follow the Post install steps in Doc.Id:

Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 [ID 1058763.1]

Do not run any of the post install instructions as those will be done after the upgrade

Rin all the post scripts after db started

1.Natively recompile PL/SQL code (optional)

2.Start the new database listener

3.De­register the original database server machine

4.Implement and run AutoConfig on the database server node

5.Re­create custom database links

6.Reconfigure the application tier to connect to the target database machine a.Update the application tier context file

b.Run AutoConfig on the application tier c.Start all application tier services

Post installation step for all addtional patches:

9858539

file are available in $ORACLE_HOME/rdbms/admin/ Run following files as sysdba

@catnomtt.sql

@catnomta.sql

@dbmsmeta.sql

@dbmsmeti.sql

@dbmsmetu.sql

@dbmsmetb.sql

@dbmsmetd.sql

@dbmsmet2.sql

@catmeta.sql

@prvtmeta.plb

@prvtmeti.plb

@prvtmetu.plb

@prvtmetb.plb

@prvtmetd.plb

@prvtmet2.plb

@catmet2.sql

­­ recompile dbms_metadata_int to enable the diffing code

alter package dbms_metadata_int compile plsql_ccflags = 'ku$xml_enabled:true';

­­ recompile dbms_metadata_util to enable the xmlschema load code

alter package dbms_metadata_util compile plsql_ccflags = 'ku$xml_enabled:true'; For Patch 13001379

(3)Postinstallation

­­­­­­­­­­­­­­­­­­­­­­

connect / as sysdba

execute sys.dbms_metadata_util.load_stylesheets; For Patch:13258936

Patch Post Installation Steps:

­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­

cd $ORACLE_HOME/ctx/admin/ctxpatch/

sqlplus / as sysdba

@ctxpatch11203.sql

For Patch:13366268

Postinstallation

­­­­­­­­­­­­­­­­­­

After you install the patch, reload the packages into the Oracle Database. SQL> ALTER SESSION SET CURRENT_SCHEMA=CTXSYS

SQL> @?/ctx/admin/drisgp.plb SQL> @?/ctx/admin/drvddl.plb SQL> @?/ctx/admin/drvxtab.plb

Validation Tasks

Verify that the application tier is configured to use the new 11gR2 database:

1.   Verify the database server hostname and database release version

2.   Go to the Oracle E­Business Suite Rapid Install Portal, and log on to the E­Business

Suite home page as the sysadmin user. Select a responsibility (such as the System

Administrator responsibility). Click on any form, such as the Concurrent­>Requests form. From the Help menu click "About Oracle Applications", and verify that the server hostname and release version correspond to those of the target database.

3.   Run Diagnostics for HTML­based Applications (Self­service)

4.   Return to the E­Business Suite home page and select the System Administration responsibility. Click on each link in the Diagnostics section.

5.   Run CRM Diagnostics

6.   Return to the E­Business Suite home page and select the CRM HTML Administrator responsibility. Click on Diagnostics, and select the Basic tab. Click on Run All Groups, and examine the test results.

|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Error Faced:

OACORE Application Log:

ignoring:null

13/03/28 18:23:23.266 html: chain failed

javax.servlet.ServletException:  java.lang.RuntimeException: Guest user/pwd does not exist or match: GUEST/ORACLE

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.EvermindPageContext.handlePageThrowable(EvermindPageContext.java:899)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.EvermindPageContext.handlePageException(EvermindPageContext.java:816)

at _AppsLocalLogin._jspService(_AppsLocalLogin.java:303)

at com.orionserver[Oracle Containers for J2EE 10g (10.1.3.4.0)

].http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)

at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462) at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594) at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)

at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)

at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)

at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.ja va:260)

at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0)

].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.j ava:303)

at java.lang.Thread.run(Thread.java:619)

13/03/28 18:40:32.219 html: 10.1.3.4.0 Stopped

Solution:

ORA­29516: AURORA ASSERTION FAILURE: CREATE OR REPLACE JAVA [ID 415780.1]