Upgrade 11i - Reduce Downtime

Hello.
We are upgrading from 11.0.3 to 11.5.9
The database is 8.1.7.4
We have done one simulation and the overall time of upgrade has been 17 days.
The server is the Sun E450: 4 processors and 2GB memory.
Seems to us that the majories problems were the Categories 3 and 4, specifically:
- Run AutoUpgrade (adaimgr) => ran for 20 hours
- Upgrade Sales and Service => ran for 30 hours
- Update Database (u2669606.drv) => ran for 95 hours !!
The database has 350GB and we can not drop any tables for reduce the database size. It is necessary to upgrade the overall database.
Has somebody some experience about upgrade and can give us any tips and tricks to reduce the downtime, please?
Has somebody some experience about upgrade on Sun E6500 server with 16 processors and 16GB memory? Is possible to estimate that the 17 days will be significantly reduced on E6500?
Thanks a lot.
[email protected]

Hi, Joel.
I am from Brazil.
Do you speak portuguese?
We are using the "Oracle Applications Release 11i(11.5.9) Part No. B10639-01" manual.
The database will be not upgrade to 9i. It continue being 8.1.7.4
Thanks.
Edson
[email protected]

Similar Messages

Guidelines to reduce downtime during upgradation R/3 to ECC6

hi all........
Here we implemented SAP R/3 4.6 in the year 2005.
Now we are planning to upgrade our system to ECC6 unicode .
We are planning to upgrade our Production and Development system to SAP
ERP6 EHP4.As part of the upgradation; we had setup a test system with the
following details:
Sun Fire 480R (UltraSparc III + 1.05GHz x 4 processor)
Memory 16 GB and Storage : Sun CSM 200 SATA HDD
SAP R/3 4.71, single code pages 1100, Oracle 9.2.0.8.0, Solaris 9
Test system with 1.2TB data copied from Production System.
We have upgraded the test system using CU&UC method ( Upgrade Guide SAPERP6.0 EHP4 SR1 Abap ). It took 2 days downtime for full upgradation and 8 days for Unicode conversion.
Requirement :
To Upgrade the current systems without any additional hardware to SAP
ERP6 EHP4 Unicode.
As a part of the above, the cluster has to be upgraded to Sun cluster
3.2, and operating system to Solaris10 (5.10)
We are having the following queries:
1. With only 1.3 TB data, we feel, the down time of 10 days is not
realistic.Though we had not deviated from the above mentioned upgrade
guide, what could be the reasons for this down time of 10 days?what arethe affecting factors? Kindly suggest the ways by which we can get
reduced downtime . The referred Notes are (784118, 855772, 952514,
936441, 954268, 864861 ) still we are unable to pin point the reason. Abreak up of this down time is given below for reference.
2. Are there any alternate approved upgradation methods to reduce
downtime in our present set up? (details of present set up is given below)
3. How to calculate the down time with reference to(sapnote:857081) to in
our setup
Current Production System Details :
System : Sun Fire V890
Processor : 1.5GHz UltraSPARC IV+ processors -- 8no.s
Memory : 64 GB
Storage : Sun Storagetek 6180: HDD FCAL(16 no.s x 450 GB)
15,000-rpm 4 Gb/sec 4GB data cache (Storage connected to server using FC
cable)
SAP : R/3 4.71 single code pages 1100
Database : Oracle 9.2.0.8 data-size is around 1.3 TB
OS : Solaris 9 (5.9)
Cluster : Sun cluster 3.1
Network : 1GB ethernet (1000BASE-SX)
Architecture : Application and database server on Same system
SAP Development system specification same as the above with 187 GB data
size. PRD and DEV systems are on cluster; PRD failover to DEV system.
The time taken for test upgrade - brief details:
1. Kernel upgraded 6.20 to 6.40 (2hours)
2. Oracle Upgrade to 10.2.0.4.0 (3.30 hours)
3. SAP UPGRADE Preparation-Apply support packages (18 hours)
4. Downtime Phase and Pre-Processing and Finalization Phase (20 hours)
5. Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB
size)(98 hours)
6. Installation of unicode system using export (95 hours)
Looking forward to hear from you.
Best Regards,
Rajeesh K.P

Hi .......
i am very sorry for late reply...............................
The time taken for test upgrade - brief details:
1. Kernel upgraded 6.20 to 6.40 (2hours)
2. Oracle Upgrade to 10.2.0.4.0 (3.30 hours)
3. SAP UPGRADE Preparation-Apply support packages (18 hours)
4. Downtime Phase and Pre-Processing and Finalization Phase (20 hours)
5. Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB
size)(98 hours)
6. Installation of unicode system using export (95 hours)
2 days downtime means the sum of time used for above 4 activities ..........................
as you suggested we can do the same 4 different down times......................
Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB size) is taking a continuous down time
of 98 hours (4.5 days ) (Activity 5)+ installation of Unicode system using the Unicode export is taking 95 hours 4.5 days
(Activity 6)
i think the we have to do activity 5 & 6 in a single stretch with out users, so it will take a continuous down time of 9 Days
With this in mind I have a few questions for you to clear a little bit more all the problem.
Q:1 Did you use more parallel jobs during Downtime than default? and I mean real Downtime where the SAP system is taken down
No.we have used default number (3 ) of parallel jobs during downtime
Did the system allow you to use ICNV (incremental converssion) for some tables?
yes we may use ICNV
Can you separate the Unicode conversion to a different weekend? or is a must for some business reason?
Yes , we can separate the Unicode conversion to a different weekend , it will not affect our business
Did you save the post download Report so you can see what are the most time consuming phases?
i am not so clear about this question , we have made an activity chart with time duration as per the test upgrade. Or how we can save the post download report from the system
Looking forward to hear from you.
Best Regards,
Rajeesh K.P

Upgrade 11i (11.5.10.2) to R12 (12.1.3)

Hi all,
I am starting to upgrade my EBS from 11.5.10.2 to 12.1.1 then to 12.1.3 on AIX 6.1 Operating System in Test instance. Any advise steps and recommendations.
I've check the Doc: Oracle EBS Upgrade Guide Release 11i to 12.1.1 and I am facing below issue :
1) Do we must to upgrade the DB to 11g as the Oracle desupport issue or want to reduce downtime?
2) Do I need apply 11i.AD.I.7 and 11.ATG_PF.H.Rup7 patches first?
3) And do I need to convert the application/DB to Multiple Organizations before upgrade? Any guideline?
4) There is no any customization, how much downtime can you experience?
The below is our system configurations :
Server : AIX 6.1 (Test instance / Prod. instance) - Single node
DB : 10.2.0.3.0 (non RAC)
APPS : 11.5.10.2 (non multi-org) :
- use Financial (GL, AP, AR, FA) only
- The lastest applied patchsets:
11i.ATG_PF.H CU2
11i.AD.I.4
11i.BNE.C
11i.FRM.F
11i.OAM.H
Forms 6.0 (Form Compiler) Version 6.0.8.27.0 (Production)
PL/SQL Version 8.0.6.3.0 (Production)
Oracle Procedure Builder V6.0.8.21.0 Build #0 - Production
Oracle Virtual Graphics System Version 6.0.5.39.0 (Production)
Oracle Multimedia Version 6.0.8.25.0 (Production)
Oracle Tools Integration Version 6.0.8.17.0 (Production)
Oracle Tools Common Area Version 6.0.5.32.0
Oracle CORE Version 4.0.6.0.0 - Production
Server version: Oracle HTTP Server Powered by Apache/1.3.19 (Unix)
Server built: Mar 25 2005 15:40:05 (iAS 1.0.2.2.2 rollup 5)
mult-org not enabled
select multi_org_flag from apps.fnd_product_groups;
--> N
I found below the list of docs, any advise steps and recommendations? And please suggest me which of the below document I need to follow?
Oracle Applications Release Notes, Release 12.1.1 [ID 798258.1]
Oracle E-Business Suite Upgrade Guide Release 11i to 12.1.1 [ID 1082375.1]
Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1]
Interesting Documents Concerning E-Business Suite 11i to R12 Upgrades [ID 850008.1]
Upgrade Advisor: E-Business Suite (EBS) Upgrade from 11.5.10.2 to 12.1.3 [ID 269.1]
Upgrade Documentation -- http://docs.oracle.com/cd/E18727_01/index.htm
Oracle E-Business Suite Installation Guide Using Rapid Install -- http://docs.oracle.com/cd/E18727_01/index.htm
Oracle E-Business Suite Release 12.1.3 Now Available
https://blogs.oracle.com/stevenChan/entry/ebs_1213_available
Thanks
Sam

1) Do we must to upgrade the DB to 11g as the Oracle desupport issue or want to reduce downtime?It is recommended you upgrade to 11.2.0.3 before you start R12 upgrade -- Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) [ID 881505.1]
2) Do I need apply 11i.AD.I.7 and 11.ATG_PF.H.Rup7 patches first?No.
3) And do I need to convert the application/DB to Multiple Organizations before upgrade? Any guideline?Yes.
https://forums.oracle.com/forums/search.jspa?threadID=&q=Multi-Org&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
https://forums.oracle.com/forums/search.jspa?threadID=&q=Multi-Org+AND+Setup&objID=c3&dateRange=all&userID=&numResults=15&rankBy=1000
4) There is no any customization, how much downtime can you experience?You can determine the downtime unless you try it yourself on an instance with a hardware that is close to your production instance.
I have one more question, do I need to download and install the following files only from https://edelivery.oracle.com/EPD/Download/get_form?egroup_aru_number=11249864 ?
A) Oracle E-Business Suite Release 12.1.1 Rapid Install Start Here
B) Oracle E-Business Suite Release 12.1.1 for IBM AIX Based Systems (64-bit) Rapid Install RDBMS
C) Oracle E-Business Suite Release 12.1.1 for IBM AIX Based Systems (64-bit) Rapid Install Databases
D) Oracle E-Business Suite Release 12.1.1 for IBM AIX Based Systems (64-bit) Rapid Install Tools
E) Oracle E-Business Suite Release 12.1.1 for IBM AIX Based Systems (64-bit) Rapid Install APPL_TOPYou need to download the following under (Oracle E-Business Suite Release 12.1.1 Media Pack for IBM AIX Based Systems (64-bit)).
From: Oracle E-Business Suite Release 12.1.1 Rapid Install Start Here (Part 1 of 4)
To: Oracle E-Business Suite Release 12.1.1 for IBM AIX Based Systems (64-bit) Rapid Install APPL_TOP - Disk 3 (Part 2 of 2)
Thanks,
Hussein

EBS upgrade 11i to R12.1.3

Hi Hussain,
we are currently on 11.5.10.2 and looking for upgrade to 12.1.3 (LATEST RELEASE)
my concern are
- i need to shortest patch for upgrade , minimize the downtime as much as possible
- can we upgrade directly to 12.1.3 without prior 12 releases?
- can we upgrade technically only and keep the functional as in 11i without changes and gradually upgrading module by module?
- please share the MOS for EBS upgrade from 11i to R12.1.3 if any.
many thanks for your help and support
regards
Raj

You will have to upgrade to 12.1.1 then upgrade to 12.1.3
Technical upgrade only won't be sufficient and you will need to consider the functional changes.
Oracle Applications Upgrade Guide: Release 11i to Release 12.1.1
http://download.oracle.com/docs/cd/B53825_03/current/acrobat/121upgrade.pdf
Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1]
New Whitepaper: Planning Your E-Business Suite Upgrade from Release 11i to 12.1
http://blogs.oracle.com/stevenChan/2010/03/ebs_121_upgrade_whitepaper.html
Oracle E-Business Suite Release 12.1.3 Now Available
http://blogs.oracle.com/stevenChan/2010/08/ebs_1213_available.html
Release Content Documents for E-Business Suite Release 12 and 12.0.x Release Update Packs [ID 404152.1]
Oracle E-Business Suite Release 12.1 Release Content Documents [ID 561580.1]
Thanks,
Hussein

Best practices to reduce downtime for Database releases(rolling changes)

Hi,
What are best practices to reduce downtime for database releases on 10.2.0.3? What DB changes can be rolling and what can't?
Thanks in advance.
Regards,
RJiv.

I would be very dubious about any sort of universal "best practices" here. Realistically, your practices need to be tailored to the application and the environment.
You can invest a lot of time, energy, and resources into minimizing downtime if that is the only goal. But you'll generally pay for that goal in terms of developer and admin time and effort, environmental complexity, etc. And you generally need to architect your application with rolling upgrades in mind, which necessitates potentially large amounts of redesign to existing applications. It may be perfectly acceptable to go full-bore into minimizing downtime if you are running Amazon.com and any downtime is unacceptable. Most organizations, however, need to balance downtime against other needs.
For example, you could radically minimize downtime by having a second active database, configuring Streams to replicate changes between the two master databases, and configure the middle tier environment so that you can point different middle tier servers against one or the other database. When you want to upgrade, you point all the middle tier servers against database A other than 1 that lives on a special URL. You upgrade database B (making sure to deal with the Streams replication environment properly depending on requirements) and do the smoke test against the special URL. When you determine that everything works, you configure all the app servers to point at B and have Streams replication process configured to replicate changes from the old data model to the new data model), upgrade B, repeat the smoke test, and then return the middle tier environment to the normal state of balancing between databases.
This lets you upgrade with 0 downtime. But you've got to license another primary database. And configure Streams. And write the replication code to propagate the changes on B during the time you're smoke testing A. And you need the middle tier infrastructure in place. And you're obviously going to be involving more admins than you would for a simpler deploy where you take things down, reboot, and bring things up. The test plan becomes more complicated as well since you need to practice this sort of thing in lower environments.
Justin

Options for fast recovery - Reducing Downtime

OS: OEL 5.7
Database : 11.2.0.3-EE (non-RAC)
I'm looking for Options using ONLY Oracle Features to reduce downtime on scheduled outages, due application changes and upgrades.
In this particular case I have only one application installed on this database (ERP).
Default Backup (full) and Restore operation are activities that we already know, but I'm looking for others options that reduce downtime.
I need a rollback plan in short time.
Any help is welcome.

Hi,
Dataguard is the best option in case of short downtime, but you will need double of storage space.
Two thing you must consider:
* What is database size?
* What is amount of data that will be updated/deleted/added during this application change?
Choose one of this option:
* Dataguard
The best option and is really fast, near zero downtime. (As mentioned by mseberg using a nice example)
* Flashback Database with RESTORE POINT
Oracle Flashback Database and restore points are related data protection features that enable you to rewind data back in time to correct any problems caused by logical data corruption or user errors within a designated time window. These features provide a more efficient alternative to point-in-time recovery and does not require a backup of the database to be restored first.
Restore points provide capabilities related to Flashback Database and other media recovery operations. In particular, a guaranteed restore point created at an system change number (SCN) ensures that you can use Flashback Database to rewind the database to this SCN. You can use restore points and Flashback Database independently or together.
You will need to open the database with RESETLOGS after FLASHBACK Database.
* Guarantee Restore Point (with flashback database disabled)
Like a normal restore point, a guaranteed restore point serves as an alias for an SCN in recovery operations. A principal difference is that guaranteed restore points never age out of the control file and must be explicitly dropped. In general, you can use a guaranteed restore point as an alias for an SCN with any command that works with a normal restore point.
A guaranteed restore point ensures that you can use Flashback Database to rewind a database to its state at the restore point SCN, even if the generation of flashback logs is disabled.
You don't need RESETLOGS after rollback.
* Edition-Based Redefinition for Online Application Maintenance and Upgrades
Edition-based redefinition enables you to upgrade a database component of an application while it is in use, thereby minimizing or eliminating down time. This is accomplished by changing (redefining) database objects in a private environment known as an edition.
To upgrade an application while it is in use, you copy the database objects that comprise the application and redefine the copied objects in isolation. Your changes do not affect users of the application—they continue to run the unchanged application. When you are sure that your changes are correct, you make the upgraded application available to all users.

Best practice to reduce downtime for fulllaod in Production system

Hi Guys ,
we have options like "Initialize without data transfer ", Initialization with data transfer"
To reduce downtime of production system for load setup tables , first I will trigger info package for Initialization without data transfer so that pointer will be set on table , from that point onwards any record added as delta record , I will trigger Info package for Delta , to get delta records in BW , once delta successful, I will trigger info package for the repair full request to get all historical data into setup tables , so that downtime of production system will be reduced.
Please let me know your thoughts and correct me if I am wrong .
Please let me know about "Early delta Initialization" option .
Kind regards.
hari

Hi,
You got some wrong information.
Info pack - just loads data from setup tables to PSA only.
Setup tables - need to fill by manual by using related t codes.
Assuming as your using LO Data source.
In this case source system lock is mandatory. other wise you need to go with early delta init option.
Early delta init - its useful to load data into bw without down time at source.
Means at same time it set delta pointer and will load into as your settings(init with or without).
if source system not able lock as per client needs then better to go with early delta init options.
Thanks

How to reduce downtime for setup table

Scenario u2013According to system data, Setup table will normally take 5 days to fill but client agreed only for max 2 days downtime. User can do change only last 3 month documents not before that. For filling 3 month data in set up table 1 day required so I have to mange options accordingly.
Datasource u2013 2LIS_13_VDITM -> DSO u2013 ZBIllIG ->Info cube
I have to Reduce Downtime for Setup table so planning following optionsu2013
1.     First run the info package for Initialization without data transfer. Then start filling setup table without blocking the User. In case Users changes any document at the time of filling setup table then these changes will move to delta queue. Once setup table filled then execute full repair request and then Delta info package.
2.     Early delta initialization u2013 no idea how to perform steps.
Please share your views with detail steps.
OLI*BW doesnu2019t have any date range in selection criteria so manually I will find out document for particular dates and use these document range.
Checked lot of post in SDN but still expecting final answer to go ahead in Production.

Hi ,
Your requirement is Billing ODS and Cube - Reset up in R/3 SYSTEM & Initialization in BW SYSTEM .
Before starting find the previous data load volume and size.
1.Go to LBWG application value=13 (Always Schedule the job in the back-ground mode)
2.Verify using tcode u2018SE16u2019 that there are NO records in u2018MC13VD0ITMSETUPu2019 table after above delete job is complete.
3.Suspend the process chain job in BW.This is to avoid it getting kicked off while the reload process is still in progress.
4.Need to check LBWQ in R/3 system for MCEX13, unprocessed Outbound queue (records). This should be empty as the last delta would have processed all.
5.Delete the initflag in BW.
6.Need to check RSA7 in R/3 SYSTEM to verify that there is NO record for 2LIS_13_VDITM    (to be done right before the Setup job).
7.Create New Info Package for Info Source '2LIS_13_VDITM' for u2018Initialize without Data Transfer Optionu2019 .Execute the package.Re-establish the Delta processing flags in R/3 and BW for the Billing TD load .
8.Save the record count for table u2018VBRPu2019 using SE16 right before the setup job.
9.Schedule Billing Data Setup Job 'OLI9BW' in R/3 SYSTEM .
10.After the Billing Setup job is complete in R/3 system, get the record count of table u2018VBRPu2019 again using u2018SE16u2019
Expeted time in R/3:5 to 7 hrs(setupjobs)
Expeted time for init and fullload : 6 hrs
ODS activation : 3hrs
Cube and with agrregates fill all : 8hrs.
Thanks,
naidu.

Upgrading 11i Payments to R12 Payments

Hi All,
We are now on Oracle EBS 11i [11.5.10.2] and Database 10g [10.2.0.4] now and we are planning to upgrade to R12.
We want to upgrade the all payment formats and templates to R12.
We have couple of questions..
1) How can we upgrade the reports(payments sent to Banks) to R12?
-- I know we need to use the e-text templates to achieve that, but my questions is , we have RDF files in R12 which fetches the data for us and have different RDF files for different layouts. So will it be the same case in R12 as well.
2) I have heard about common data extract in R12, how do we get that, what all changes needs to be done for that to have common data extract for all the Layouts(Templates).
Can you also please share if there is any document created to achieve this requirement.
Thanks,
S.

Duplicate Post. See answer here:
Re: Upgrading 11i Payments to R12 Payments
Regards,
Gareth
http://garethroberts.blogspot.com

Ways to reduce downtime for filling up setup table

Hi Experts,
Can anyone tell me the step by step process so that i can reduce downtime for filling up setup tables?
I know that setup tables can be filled by considering sales document numbers....but the further steps are not clear with me...........specially with data loadin till PSA and then to ODS/Cube
So plz throw some light on this.......
Regards,
Vaishnavi.

Hi,
You will need to fill the set up tables in 'no postings period'. In other words when no trasnactions are posted for that area in R/3 otherwise those records will not come to BW. Discuss this with end user and decide. Weekends are a general choice for this activity.
You can run them after business hours so that there wont be any transactions, or in the night times or you can do it on week ends so that there is no need to take down time.
Fill the setup tables with already closed values and then fill up again with open values.This will reduce the down time.
Initialize closed periods first in which users wont enter data ( for example in 2007 or 2006), this initializations can be done while users are working. Then the initialize last period at night/weekends.holidays etc.
If you know documents that are in closed periods, and you are sure that these documents can no longer be changed, you can only fill the SetUp tables for these documents or only for these periods, by continuing to post in open periods. You then initialize only for these intervals, delete the setup table, and only then do you fill the setup table with the rest of the documents this procedure can drastically reduce the downtimes of your system.
However, there is a risk that user exits (and in LIS, formulas and conditions) can be used to retrieve documents that are in periods that are already "closed periods".
One more thing what you need to bear in mind is, to check if there are any Scheduled jobs which are updating the transaction tables, which would definitely cause Data Reconciliation Issues.
Try Early Delta Initialization
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
Extractors that support early delta initialization are delivered with Plug-Ins as of Plug-In (-A) 2002.1.
You cannot run an initialization simulation together with an early delta initialization.
Hope this link may make you clear about Early Delta Initialization
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
http://www.allinterview.com/showanswers/2907.html
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/early-delta-initialization-459379
http://books.google.co.in/books?id=qYtz7kEHegEC&pg=PA293&lpg=PA293&dq=early+delta&source=web&ots=AM1PtX6wcZ&sig=xKOF85Gb8UtszY44zt06K6R0n3M&hl=en#PPA290,M1
http://www.blackwellpublishing.com/journal.asp?ref=1069-6563&site=1
EARLY DELTA
Early delta Initialization
How To Minimize Downtime For Delta Initialization
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6
How To Minimize Effects of Planned Downtime (NW7.0)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb
Note 753654 - How can downtime be reduced for setup table update
602260 - Procedure for reconstructing data for BW
437672 - LBWE: Performance for setup of extract structures
436393 - Performance improvement for filling the setup tables
Note 739863
/thread/756626 [original link is broken]
Re: How to Setup and INIT from 2LIS_13_VDITM with millions of records
How downtime can be reduced for setup table update.
Fill setup tables without locking users
Initialization Setup Tables.
Hope this helps.
Thanks,
JituK

Any one really use mw to upgrade 11i to R12?

any one is really ising mw to upgrade 11i to R12?

Yes we have many customers using Maintenance Wizard for their upgrades.

Upgrade 11i.ATG_PF.H.delta.2 to 11i.ATG_PF.H.delta.7

Hi All,
Can we upgrade 11i.ATG_PF.H.delta.2 to 11i.ATG_PF.H.delta.7 directlly.? Please suggest.
I hav gone through the metalin doc id Doc ID 783600.1 but could not get hint.
Please help me out on this.
Thanks in advance.

Can we upgrade 11i.ATG_PF.H.delta.2 to 11i.ATG_PF.H.delta.7 directlly.? Please suggest.Yes -- Make sure you meet the requirements under "Before you apply this patch" section.
Please also consider the patches in (Known Issues On Top of 11i.ATG_PF.H.delta.7 (RUP7) - 6241631 [ID 858801.1]).
Thanks,
Hussein

Upgrade Fails in downtime Phase - MAIN_SWITCH/PARMVNT_XCNV

Dear All,
We are working on the upgrade from ECC6.0 to ECC6.0 with EHP4 and now running in the downtime phase. In the downtime phase, the upgrade stopped in the phase of MAIN_SWITCH/PARMVNT_XCNV and stated that to check the logs of MVNTXCNV.ELG. In the log file it stated that
MVNTXCNV.ELG
MVNTTABS ERRORS:ddlntabs and RETURN CODE in PD000825.FSO
SQL -error Duplicate name:SRT_MONLoG_DATA2 in DDL st
SRT_MONLOG_DATA2
error in DDL nametab for "SRT_MONLOG_DATA2 not activated
Then I have searched in SMP and in SDN and came to know that we need to implement the notes of
Note 1399438 - System upgrade stops in phase XCNV
Note 1310677 - System upgrade terminates in phase MAIN_SWITCH/PARMVNT_XCN
Hence, I have started the instance manually and unlocked the tp to login as different user for applying this note ( Because we cannot apply note usign DDIC ) . Then able to login into the system and downloaded the notes as well,
While implementing the when I try to create a request - it immediately throwing a short dump and dump states that
TRINT_INSERT_COMM_HEADER
SQL error in the database when accessing a table
Database error text: POS(40) too few values
Internal call code: RSQL/INSR/EO70C
Please check the same in SM21
In system logs the logs says that
Runtime error DBIF_RSQL_SQL_ERROR
Short dump created
Database error -1200 at PRE access to table E070c
POS (40) Too few values
Instead of creating a new request and tried to use own request but the results are same, Also i tried to change the client settings from automatic recording of changes and also changes w/o automatic recording of changes - but both are giving the same output.
Is there any other possibility to get rid off this issue? Any suggestions are highly appreciated
Regards
Vijay

Its fixed and I have just implemented the note 589296 - Solved our issue
select * from "SAPFSO"."DDXTT~" where TABNAME = 'SRT_MONLOG_DATA2'
or
select * from "SAPFSO"."DDXTT" where TABNAME = 'SRT_MONLOG_DATA2'
Check it approximately it should return with the FLAG value as F
update "SAPFSO"."DDXTT~" set modeflag = 'A' where TABNAME = 'SRT_MONLOG_DATA2'
Thanks for your support
Regards
Vijay

How to Upgrade 11i Database from 10.2.0.2 to 10.2.0.3

Hi Friends,
I have 11i database with (10.2.0.2)...now i want to upgrade my database to 10.2.0.3.....
I have gone through the 10.2.0.3 pre instalaltion tasks....Do we again need to run the DBUA from 10g Oracle Home....
Please suggest

You can use one of the following for upgrading an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.3:
- Upgrading a Release 10.2 Database using Oracle Database Upgrade Assistant (Run dbua)
- Manually Upgrading a Release 10.2 Database (Run catupgrd.sql)
For more details, please check "Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.3" section of the readme file of 10.2.0.3 patch (Patch 5337014).

Upgrade 11i to R1212 on zLinux

I am trying to upgrade Oracle Apps 11i to R12 and I am hitting the following issue when I apply the upgrade patch.
Apps ver: 11510 CU2
DB: 11203
Err from the worker log:
Unable to process file in PACKAGE mode.
Not converting file for Invoker's Rights because it appears to
be a package body creation script (based on the filename).
File is: /scratch/marshad/R1213/apps/apps_st/appl/ont/12.0.0/patch/115/sql/OEXCRSHB.pls
sqlplus -s APPS/***** @/scratch/marshad/R1213/apps/apps_st/appl/ont/12.0.0/patch/115/sql/OEXCRSHB.pls
CREATE or REPLACE PACKAGE BODY OE_RSCH_SETS_CONC_REQUESTS AS
ERROR at line 1:
ORA-03113: end-of-file on communication channel
ERROR:
ORA-03114: not connected to ORACLE
ERROR:
ORA-03114: not connected to ORACLE
ERROR:
ORA-03114: not connected to ORACLE
ERROR:
ORA-03114: not connected to ORACLE
UPDATE fnd_install_processes
SET status = 'F'
WHERE worker_id = 1
AD Worker error:
Error while deleting row from ad_util_params.
AD Worker error:
ORA-03114: not connected to ORACLE
Error while calling aidjawkExitJavaWorker()
+++++++++++++++++++++++++++++++++++
From the DB alert log:
Errors in file /scratch/marshad/R1213/diag/R11I/diag/rdbms/r11i/R11I/trace/R11I_ora_20584.trc (incident=27282):
ORA-07445: exception encountered: core dump [kgldpo0()+812] [SIGSEGV] [ADDR:0x0] [PC:0x86FAC498] [Address not mapped to object] []
Use ADRCI or Su
++++++++++++++++++++++++++++++++++
Any pointers...

1) DB is up and running and I am able to connect to DB. I am able to connect to db without any issues..
2)/scratch/marshad/R1213/diag/R11I/diag/rdbms/r11i/R11I/trace/R11I_ora_20584.trc (incident=27282):
System name: Linux
Node name: ********************
Release: 2.6.18-164.el5
Version: #1 SMP Tue Aug 18 15:53:50 EDT 2009
Machine: s390x
Instance name: R11I
Redo thread mounted by this instance: 1
Oracle process number: 23
Unix process pid: 20584, image: ******************
*** 2011-12-30 03:57:28.970
*** SESSION ID:(318.36791) 2011-12-30 03:57:28.970
*** CLIENT ID:() 2011-12-30 03:57:28.970
*** SERVICE NAME:(SYS$USERS) 2011-12-30 03:57:28.970
*** MODULE NAME:(SQL*Plus) 2011-12-30 03:57:28.970
*** ACTION NAME:() 2011-12-30 03:57:28.970
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x0, PC: [0x86fac498, kgldpo0()+812] [flags: 0x0, count: 1]
ssdgetcall: WARNING! Wrong backchain value during unwind. old=0x8b854958 new=0x3b
DDE: Problem Key 'ORA 7445 [kgldpo0()+812]' was flood controlled (0x6) (incident: 27282)
ORA-07445: exception encountered: core dump [kgldpo0()+812] [SIGSEGV] [ADDR:0x0] [PC:0x86FAC498] [Address not mapped to object] []
ssdgetcall: WARNING! Wrong backchain value during unwind. old=0x8b854958 new=0x3b
ssexhd: crashing the process...
Shadow_Core_Dump = PARTIAL
ksdbgcra: writing core file to directory '/scratch/marshad/R1213/diag/R11I/diag/rdbms/r11i/R11I/cdump'
3) Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool [ID 153788.1] gives ORA-7445 (kgldpo0) (Doc ID 959339.1) which does not provide any useful information.

Upgrade 11i - Reduce Downtime

Similar Messages

Maybe you are looking for