Database upgrade time.

I'm running an upgrade from Oracle9i to 10g. So far it's going well. I'm at the part where my old database is being converted to 10g. The DB is around 16GB's in size and right now I'm going on 9 hours of "conversion". The progress bar is at 85%.
Does this sound about right for the size of DB I have?
The load on the box doing the upgrade is very low and there is almost no CPU activity (as observed by top). If I physically go and look at the server itself, the hard drive is completely inactive for the most part.
Just seems like a DB upgrade would be a bit more processor or disk I/O intensive!
Anyways, appears it should be done in the next few hours at the rate it's going.
Thanks.

Just a follow up on this. It's been nearly two and a half hours, and the progress bar is still stuck at 85% :-(
Guess it's hung.
Don't see any reference in the manual on what to do if this fails, so I guess my only option is to abort the upgrade and start it over again.
Good thing this is a test run on a test server. :-)

Similar Messages

Oracle DataBase Upgradation Time

Hello Experts,
Database size is 97GB,
I want to Upgrade database from 10.2.0.1.0 To 10.2.0.2.0.
How much time it will take for Upgradation process ??.
Thanks,
Rahul S.S.

Why not upgrade to 10.2.0.5 instead .... ???
No we cant do that its not a suported version from SAP.
Only option you have is 10.2.0.2 or 10.2.0.4 or else is 11.2.0
Also as mentioned in above thread 10.2.0.1 was never supported, may be you want to upgrade to 10.2.0.4 which may be a job of hours , but always depends upon your skills as well.
Regards,

11.5.10.2 12.1.1 and 10g 11g database upgrade at same time

I have just started an 11.5.10.2 > 12.1.1 upgrade and have created a project in MWIZ 2.15 for it.
I would also like to upgrade the 10.2.0.2 database to 11.1.0.7 as part of the same upgrade and create an MWIZ project for that.
I have a couple of questions that the MWIZ FAQ does not address:
1. At what point in the 11.5.10.2 > 12.1.1 upgrade should I do the database upgrade?
MWIZ has two points when it can be done based on apps/database versions. One is at the end of the 'Prep for Upgrade' category and the other is during the 'Upg to Rel 12.1.1' category. The MWIZ step notes cover upgrading to the latest 10g or 11g patch version but not upgrading from 10g to 11g so I am unsure which category to go for.
2. When I create the database upgrade project which 'Destination Version' should I choose?
The two options are 'RDBMS 11.1 and E-Business Suite 11.5' and 'RDBMS 11.1 and E-Business Suite 12'.
As I haven't upgraded to R12 yet and am still at the pre-upgrade stage should I pick 11.5? Or should I go with R12 because I am upgrading Apps and the database at the same time?
Any help and advice gratefully received.
Thanks

Answer to above question not required now as:
Having read the 24th December update of note 761570.1 - 'Database Preparation Guidelines for an Oracle E-Business Suite Release 12.1.1 Upgrade' I have decided to upgrade the database to 11.2.0.x by following the Path C option.
Unfortunately as the 11.2.0.x upgrade isn't covered by MWIZ yet I will have to follow the manual steps.

IPhoto needs to be upgraded everytime I open it. Then it finds consistences. I have rebuilt the database many times

iPhoto needs to be upgraded everytime I open it. Then it finds consistences. Then it repairs the database.
I have also rebuilt the database many times useing command + alt.
Now it shows every event three times. If I delete one version of that event, it deletes them all.
Then next time I open iPhoto it needs updateing and repairing again
I have used disk utility to repair permissions

Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.

Zen 4 - Zen 6.5 Inventory database upgrade fails

Hi all,
Have installed Zen 6.5 over a Zen 4 server (nw65) running inventory.
Database is on a seperate oracle server.
When I start inventory, it starts the database upgrade and then fails
with a java exception part way through, and then says "stopping the
upgrade service".
Following is the log. Anyone know which bit is falling over and why?
There's a few errors in the log and I don't know which are cosmetic/non
critical. Either way, I've researched each and can't find any fixes
anyway.
cheers
Dave
[12/8/05 14:58:40.307] ZENInv - Server Config: The severconfig service
start is pending...
[12/8/05 14:58:40.464] ZENInv - Server Config: Getting Cascade INit
time
[12/8/05 14:58:41.462] ZENInv - Server Config: Database Location
Policy DN is CN=Server Package - DAN02:General:ZENworks
Database.OU=POLICIES.OU=APPLICATIONS.O=CHISHOLM
[12/8/05 14:58:43.573] ZENInv - Server Config: The severconfig service
is started...
[12/8/05 14:58:43.707] ZenInv - Upgrade Service: Info : Read
zenInvComponentStatus = 6.5 12 0
[12/8/05 14:58:43.707] ZenInv - Upgrade Service: Inventory Server
zenInvComponentStatus = 6.5 12 0
[12/8/05 14:58:43.720] Service Manager: start(ServiceDataAccessor,
String[]) not found in
'com.novell.zenworks.desktop.inventory.storer.Stor erServiceInit'
[12/8/05 14:58:43.740] ZENInv - Storer: Start with
'ServiceStatusChangeListener' invoked
[12/8/05 14:58:44.824] ZenInv - Upgrade Service: Unzipping the file
migrate.zip
[12/8/05 14:58:46.718] ZenInv - Upgrade Service: Transforming the
Migration SQL files...
[12/8/05 14:58:51.768] ZENInv - Storer: zenworks.isClosed =true
[12/8/05 14:58:53.699] ZENInv - Storer: The current NDS tree=CIT
[12/8/05 14:58:53.724] ZENInv - Storer: Storer from dblocation user:
MW_DBA driver: oracle.jdbc.driver.OracleDriver protocol: jdbc:oracle:
subname: thin:@ port: 1522
[12/8/05 14:58:53.728] ZENInv - Storer: url[From DBObject]:
jdbc:oracle:thin:@ora01a.chisholm.vic.edu.au:1522: dw
[12/8/05 14:58:53.756] ZENInv - Storer: wsdn:
CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLMi = 0
[12/8/05 14:58:53.973] ZENInv - Storer: Loading Storer test properties
file
[12/8/05 14:58:54.053] Service Manager: start(ServiceDataAccessor,
String[]) not found in
'com.novell.zenworks.desktop.inventory.strconverte r.STRConverterServiceInit'
[12/8/05 14:58:54.059] ZENInv - STRConverter: Start with
'ServiceStatusChangeListener' invoked
[12/8/05 14:58:54.755] ZENInv - Status Reporting: Messages are written
into XML file for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:58:54.914] ZENInv - Status Reporting: Number of records to
add are: 1 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:58:55.012] ZENInv - Status Reporting: Adding record 0 for
DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:58:55.729] ZENInv - Status Reporting: Number of modified
records are: 0 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:58:55.780] ZENInv - Storer: Database is not
initialized..will retry after 300 seconds
[12/8/05 14:58:55.787] ZENInv - Storer: Storer: Database not
initialized as it is being upgraded ...will retry after 300 seconds.
[12/8/05 14:58:55.788] ZENInv - Status Reporting: Messages are written
into XML file for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:58:55.826] ZENInv - Status Reporting: Number of records to
add are: 1 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:58:55.860] ZENInv - Status Reporting: Adding record 0 for
DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:58:57.439] ZENInv - Status Reporting: Number of modified
records are: 0 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:59:04.100] ZENInv - STRConverter: Loading STRConverter test
properties file
[12/8/05 14:59:04.201] Service Manager: start(ServiceDataAccessor,
String[]) not found in
'com.novell.zenworks.desktop.inventory.senderrecei ver.control.ReceiverServiceInit'
[12/8/05 14:59:15.618] ZENInv - SendRec Common: entPushDir =
SYS:\ZENworks\Inv\ScanDir\EntPushDir
[12/8/05 14:59:15.618] ZENInv - SendRec Common: entMergeDirD =
SYS:\ZENworks\Inv\ScanDir\EntMergeDir
[12/8/05 14:59:15.618] ZENInv - SendRec Common: dbDirD =
SYS:\ZENworks\Inv\ScanDir\DbDir
[12/8/05 14:59:15.625] ZENInv - SendRec Common: serverName = DAN02
[12/8/05 14:59:15.626] ZENInv - SendRec Common: serviceDN =
CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:59:15.626] ZENInv - SendRec Common: treeName = CIT
[12/8/05 14:59:15.626] ZENInv - SendRec Common: hasSSD = false
[12/8/05 14:59:15.626] ZENInv - SendRec Common: hasISD = false
[12/8/05 14:59:15.626] ZENInv - SendRec Common: hasESD = true
[12/8/05 14:59:15.632] ZENInv - SendRec Common: hasDB = true
[12/8/05 14:59:15.633] ZENInv - SendRec Common: securityDir =
SYS:\PUBLIC\ZENWORKS\WMINV\PROPERTIES
[12/8/05 14:59:15.661] Service Manager: start(ServiceDataAccessor,
String[]) not found in
'com.novell.zenworks3x.desktop.inventory.senderrec eiver.control.ReceiverServiceInit'
[12/8/05 14:59:15.882] ZENInv - CascadedBaseTime Server:
zenInvCascadeBaseTimeService: CBTServiceController: Startup Properties:
{basetime=Thu Jan 01 10:00:00 EST 1970,
servicename=zenInvCascadeBaseTimeService, portnumber=0}
[12/8/05 14:59:16.367] ZENInv - IFS Server: zeninvReceiverService:
FileServiceController: Startup Properties: {chunksize=4096,
transfers=100,
rootdirectory=SYS:\ZENworks\Inv\ScanDir\EntPushDir \ZipDir,
timeout=60000, servicename=zeninvReceiverService, portnumber=0}
[12/8/05 14:59:25.771] ZENInv - TCPReceiver: cascadingBaseTime = 0
[12/8/05 14:59:25.771] ZENInv - TCPReceiver: entPushDir =
SYS:\ZENworks\Inv\ScanDir\EntPushDir
[12/8/05 14:59:25.777] ZENInv - TCPReceiver: serverName = DAN02
[12/8/05 14:59:25.777] ZENInv - TCPReceiver: serviceDN =
CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:59:25.777] ZENInv - TCPReceiver: treeName = CIT
[12/8/05 14:59:25.778] ZENInv - TCPReceiver: hasDB = true
[12/8/05 14:59:25.971] Service Manager: start(ServiceDataAccessor,
String[]) not found in
'com.novell.zenworks.common.inventory.dictionaryup date.provider.DictProvider'
[12/8/05 14:59:26.005] ZENInv - TCPReceiver: Receiver Started without
CLUSTER
[12/8/05 14:59:26.006] ZENInv - TCPReceiver: Receiver Binds to Port
Number : 65432
[12/8/05 14:59:26.073] ZENInv - IFS Server: zenInvDictProvider:
FileServiceController: Startup Properties: {chunksize=4096,
transfers=100, rootdirectory=SYS:\ZENworks\Inv\server\DictDir,
timeout=60000, servicename=zenInvDictProvider, portnumber=0}
[12/8/05 14:59:26.183] Service Manager: start(ServiceDataAccessor,
String[]) not found in
'com.novell.zenworks.common.inventory.dictionaryup date.consumer.DictConsumer'
[12/8/05 14:59:28.918] ZENInv - Dictionary Consumer:
DictConsumerUtility::getUpdatePolicyDN: getDictionaryUpdatePolicy
returned attribs.returnValue = 0
[12/8/05 14:59:28.919] ZENInv - Dictionary Consumer:
DictConsumerService::DictDownloadThread::run:
UpdatePolicyNotFoundException.
com.novell.zenworks.common.inventory.dictionaryupd ate.consumer.UpdatePolicyNotFoundException
at
com.novell.zenworks.common.inventory.dictionaryupd ate.consumer.DictConsumerUtility.getUpdatePolicyDN (DictConsumerUtility.java:237)
at
com.novell.zenworks.common.inventory.dictionaryupd ate.consumer.DictConsumerService$DictDownloadThrea d.setUpdatePolicyAttribs(DictConsumerService.java: 688)
at
com.novell.zenworks.common.inventory.dictionaryupd ate.consumer.DictConsumerService$DictDownloadThrea d.getFileClientProperties(DictConsumerService.java :616)
at
com.novell.zenworks.common.inventory.dictionaryupd ate.consumer.DictConsumerService$DictDownloadThrea d.transferFiles(DictConsumerService.java:429)
at
com.novell.zenworks.common.inventory.dictionaryupd ate.consumer.DictConsumerService$DictDownloadThrea d.run(DictConsumerService.java:211)
[12/8/05 14:59:28.921] ZENInv - Status Reporting: Messages are written
into XML file for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:59:28.953] ZENInv - Status Reporting: Number of records to
add are: 1 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:59:28.986] ZENInv - Status Reporting: Adding record 0 for
DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:59:29.326] ZENInv - Status Reporting: Number of modified
records are: 0 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:59:29.326] ZENInv - Dictionary Consumer:
DictConsumerService::FileDownloadListener::downloa dFailed.
[12/8/05 14:59:59.680] ZenInv - Upgrade Service: Starting Schema
Migration
[12/8/05 14:59:59.751] ZenInv - Upgrade Service: mw_dba->alter
tablespace cim3 default storage (maxextents unlimited) is being
executed
[12/8/05 14:59:59.752] ZenInv - Upgrade Service: Could not do the
operation. details:ORA-25143: default storage clause is not compatible
with allocation policy
ErrorCode:25143
[12/8/05 14:59:59.752] ZenInv - Upgrade Service: Totaltime taken for
Schema Migration : 38
[12/8/05 14:59:59.851] ZENInv - Storer: cim.isClosed =true
[12/8/05 14:59:59.937] ZENInv - Status Reporting: Messages are written
into XML file for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 14:59:59.970] ZENInv - Status Reporting: Number of records to
add are: 1 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:00.133] ZENInv - Status Reporting: Adding record 0 for
DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:00.277] ZENInv - Status Reporting: Number of modified
records are: 0 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:00.719] ZenInv - Upgrade Service: migrateDbToMidas(true)
failed in AlterProcedure
[12/8/05 15:00:00.728] ZENInv - Status Reporting: Messages are written
into XML file for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:00.761] ZENInv - Status Reporting: Number of records to
add are: 1 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:00.795] ZENInv - Status Reporting: Adding record 0 for
DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:00.964] ZENInv - Status Reporting: Number of modified
records are: 0 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:00.966] ZenInv - Upgrade Service: Upgrade database to
ZENworks 6.5 failed. Reinstall ZENworks 6.5 and start the inventory
server again
[12/8/05 15:00:00.967] ZENInv - Status Reporting: Messages are written
into XML file for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:01.000] ZENInv - Status Reporting: Number of records to
add are: 1 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:01.038] ZENInv - Status Reporting: Adding record 0 for
DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:01.188] ZENInv - Status Reporting: Number of modified
records are: 0 for DN=CN=DAN02_ZenInvService.OU=DAN.O=CHISHOLM
[12/8/05 15:00:01.237] ZenInv - Upgrade Service: [EnumModifier]
modifyEnumTables, Running EnumModifier in integrated mode with
upgradeService
[12/8/05 15:00:01.237] ZenInv - Upgrade Service: [EnumModifier]
modifyEnumTables, dbDriver:oracle.jdbc.driver.OracleDriver
[12/8/05 15:00:01.237] ZenInv - Upgrade Service: [EnumModifier]
modifyEnumTables,
dbURL:jdbc:oracle:thin:@ora01a.chisholm.vic.edu.au :1522:dw
[12/8/05 15:00:01.239] ZenInv - Upgrade Service: [EnumModifier]
modifyEnumTables, dbType:1
[12/8/05 15:00:01.239] ZenInv - Upgrade Service: [EnumModifier]
modifyEnumTables, dbUser:MW_DBA
[12/8/05 15:00:01.239] ZenInv - Upgrade Service: [EnumModifier]
modifyEnumTables, dbPasswd:novell
[12/8/05 15:00:01.248] ZenInv - Upgrade Service: [EnumModifier] Product
Version: ZFD 4
[12/8/05 15:00:01.298] ZenInv - Upgrade Service: [EnumModifier]
checkConditions(), Executing check 'Statements':5
[12/8/05 15:00:01.298] ZenInv - Upgrade Service: [EnumModifier]
DatabaseEnumsModifier::checkResult(), query: insert into
cim.upgrademethod_en_US Values (13, 'Socket 423')
[12/8/05 15:00:01.311] ZenInv - Upgrade Service: [EnumModifier]
checkResult, errorcode:1
[12/8/05 15:00:01.311] ZenInv - Upgrade Service: [EnumModifier]
checkResult, Non-fatal error:1
[12/8/05 15:00:01.312] ZenInv - Upgrade Service: [EnumModifier]
DatabaseEnumsModifier::checkResult(), query: insert into
cim.upgrademethod_en_US Values (14, 'Socket A (Socket 462)')
[12/8/05 15:00:01.316] ZenInv - Upgrade Service: [EnumModifier]
checkResult, errorcode:1
[12/8/05 15:00:01.316] ZenInv - Upgrade Service: [EnumModifier]
checkResult, Non-fatal error:1
[12/8/05 15:00:01.317] ZenInv - Upgrade Service: [EnumModifier]
DatabaseEnumsModifier::checkResult(), query: insert into
cim.upgrademethod_en_US Values (15, 'Socket 478')
[12/8/05 15:00:01.321] ZenInv - Upgrade Service: [EnumModifier]
checkResult, errorcode:1
[12/8/05 15:00:01.322] ZenInv - Upgrade Service: [EnumModifier]
checkResult, Non-fatal error:1
[12/8/05 15:00:01.322] ZenInv - Upgrade Service: [EnumModifier] Da

ok putting inv into "ALL" debug mode, it told me it was running
init_sl_0.sql
I found this file contained in migrate.zip under the wminv\properties
directory.
So I extracted the migrate.zip file, edited init_sl_0.sql and removed
the alter tablespace lines. Why they're wanting to do alter tablespace
I have no idea - applications shouldn't expect to be able to do that...
it's up to the organisation and the DBA to manage the tablespaces, not
the application.
I then re-zipped all the files using Winzip and named the file
migrate.zip and placed it in the properties directory.
Now, when the upgrade runs I get a java exception when it tries to
unzip migrate.zip and the upgrade bombs.
I also tried just opening the migrate.zip file with Winzip and directly
editing the file from within Winzip, which does allow for this. However
it appears the files inside the archive are flagged read-only, so
Winzip can't rewrite the edited file back into the same folder location
within the archive.
Here's the java exception:
***12/21/05 16:24:40.789] ZenInv - Upgrade Service: Unzipping the file
migrate.zip
[12/21/05 16:24:40.827] ZenInv - Upgrade Service:
[12/21/05 16:24:40.827] ZenInv - Upgrade Service: Exception while
unzipping the migration zip file
java.lang.NullPointerException
at
com.novell.zenworks.desktop.inventory.upgradeServi ce.MigUnzip.unZipFile(AlterProcedure.java:4557)
at
com.novell.zenworks.desktop.inventory.upgradeServi ce.MigUnzip.unzip(AlterProcedure.java:4522)
at
com.novell.zenworks.desktop.inventory.upgradeServi ce.AlterProcedure.unzipMigrateZipFile(AlterProcedu re.java:1983)
at
com.novell.zenworks.desktop.inventory.upgradeServi ce.AlterProcedure.unzipMigrateZipFile(AlterProcedu re.java:1975)
at
com.novell.zenworks.desktop.inventory.upgradeServi ce.UpgradeServiceController.aInitMigration(Upgrade ServiceController.java:218)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
com.novell.zenworks.desktop.inventory.senderreceiv er.statemachine.StateMachine.execute(StateMachine. java:68)
at
com.novell.zenworks.desktop.inventory.upgradeServi ce.UpgradeServiceController.init(UpgradeServiceCon troller.java:113)
at
com.novell.zenworks.desktop.inventory.upgradeServi ce.UpgradeServiceThread.run(UpgradeServiceThread.j ava:81)
[12/21/05 16:24:40.828] ZenInv - Upgrade Service: unzipMigrateZipFile()
failed in AlterProcedure
[12/21/05 16:24:40.829] ZenInv - Upgrade Service: in aLogError() method
[12/21/05 16:24:40.830] ZenInv - Upgrade Service: Upgrade database to
ZENworks 6.5 failed. Reinstall ZENworks 6.5 and start the inventory
server again
Ok.. what am I doing wrong ? :) It shouldn't be this hard....
cheers
Dave

Database Upgrade 10.1.0.4 to 10.2.0.4

Newbie here.
So I am starting to use OEM on Windows XP workstation and have upgraded it to 10.2.0.4 and also wanted to upgrade the repository to 10.2.0.4 as well.
So this is what I have done so far.
I have installed 10.2.0.1 into a new home. I have patch it to 10.2.0.4. I am using DBUA to upgrade the database and have set my ORACLE_HOME to the new home and started DBUA. Everything is working just fine until the new OracleService is created and is trying to start. I received a message that it is unable to start service. If i click on continue I received the ORA-12560 TNS error. I have tried multiple times to get this to work and it always fails on this part..
Also to let you know that when I connect to SQLPlus before upgrade I have to connect using sysplus sysman/xxxxx@emrep with out emrep it won't connect. I have also set TNS_ADMIN to the original homes network/admin directory.
I have research the documentation on upgrading, but maybe I am missing a step or someone has run into the same issue.
Any help you can lend me would be appreciated.

The database files won't be copied over. As general practice, databases aren't stored under Oracle Homes. You could always fix that by moving the database, backup the control file to trace, and edit it with new file locations. I wouldn't worry about that right now.
Did you run the prerequisite script before trying to upgrade?
<10.2 HOME>/rdbms/admin/utlu102i.sql
Once a database is opened upgrade, you won't be able to open it with the old binaries.
Was the listener up when you tried to connect to it with 10.1? Were there any errors?
The manual process of upgrading the database is to export the 10.2 env, open the database upgrade, upgrade the data dictionary <10.2HOME>/rdbms/admin/catupgrd.sql, startup the database normally, and Compile all the invalid objects <10.2HOME>/rdbms/admin/utlrp.sql. I would make sure to go over the sql that executes prerequisite checks and read through the upgrade docs. I would also take a backup before doing anything.

Database upgrade from 10.2.0.3.0 to 11.1.0.7

Hi All,
OS:linux 86x64 Red Hat linux
We would like to perform Database upgrade from 10.2.0.3.0 to 11.1.0.7.
I do have quick questions regarding the upgrade.
1. When we upgrade the Database to version 11, do we need to update the client also? What is Oracle recommendation?
2. Do we need to take any DB backup before the upgrade?
3. How will the OBIEE windows box ODBC connect to the upgraded 11 g instance? Will the version 10 driver work to connect to version 11 databases?
4. We have Informatica,DAC in the existing instance. Will the DB upgrade have any impact on them?
Could anyone please share their experience/thoughts on the above like the steps to perform the upgrade.
Thanks for your time!

Hi,
Hi All,
OS:linux 86x64 Red Hat linux
We would like to perform Database upgrade from 10.2.0.3.0 to 11.1.0.7.
I do have quick questions regarding the upgrade.
1. When we upgrade the Database to version 11, do we need to update the client also? What is Oracle recommendation?Just 11g upgrade will include all cient/Server tools on you Linux Box. On client side its recommended to upgrade client version 11.1.0.7.
Please refer MOS tech note:
*Oracle 10g Client Connecting To Oracle 11g Database Gets ORA-01017 invalid username/password [ID 888432.1]*
2. Do we need to take any DB backup before the upgrade?Yes, perform full cold backup of Database as well as 10G $ORACLE_HOME binaries including inventories.
3. How will the OBIEE windows box ODBC connect to the upgraded 11 g instance? Will the version 10 driver work to connect to version 11 databases?AFAIK, it should work. What is the version of OBIEE?
4. We have Informatica,DAC in the existing instance. Will the DB upgrade have any impact on them?Again AFAIK, there should not be any effect. I would recommend you to log a S.R and verify the same from support.
thanks,
X A H E E R
http://appsdbaworkshop.blogspot.com

Impact of database upgrade in Bw delta queue

Hi Gurus,
We are going to upgrade the R/3 oracle database. I suppose that it have an impact in the BW delta queue, and that before the upgrade the logistics queues should be uploaded to BW.
I'm right? exits some note or some checklist about wihch activities should be performed in BW due to the database upgrade?
Thanks in advance for your help.

Hi,
This speaks about support pack upgrade. But i think this also applies for DB upgrade too.
Its always better to drain the delta queues before an upgrade.
As a standard practice we drain the delta queues by running the IP/ chain multiple times.
As a prerequiste we cancel/reschedule the V3 jobs to a future date during this activity.
The V3 extraction delta queues must be emptied prior to the upgrade to avoid any possible data loss.
V3 collector jobs should be suspended for the duration of the upgrade.
They can be rescheduled after re-activation of the source systems upon completion of the upgrade.
See SAP Notes 506694 and 658992 for more details.
Page 17
Load and Empty all Data mart Delta Queues in SAP BW. (e.g. for all export DataSources)
The SAP BW Service SAPI, which is used for internal and BW to BW data mart extraction, is
upgraded during the SAP BW upgrade. Therefore, the delta queues must be emptied prior to the
upgrade to avoid any possibility of data loss.
upgrade preparation and postupgrade checklist
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
/message/3221895#3221895
OSS notes 328181 and 762951 as a prerequisites.
Failure to follow the instructions in those notes may probably result in data loss.
https://websmp207.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700002662832005E
/thread/804820
Effect on BW of R/3 Upgrade
How To Tackle Upgrades to SAP ERP 6.0
/people/community.user/blog/2008/03/20/how-to-tackle-upgrades-to-sap-erp-60
thanks,
JituK

Cant deploy in OWB 9.2.0.4.0 after database upgradation

We are facing a problem with OWB 9.2.0.4.0 after the database is upgraded from[b] oracle 9.2.0.1.0 to 9.2.0.8.0.
Initially OWB 9.2.0.4.0 was working fine with oracle 9.2.0.1.0 (i.e. the owb runtime and target schema was in this database) but due to some urgent requirement we need to upgrade the database to oracle 9.2.0.8.0. After the oracle upgradation we cant deploy any ETL object from the OWB design(9.2.0.4.0) to the runtime. Also we cant create any new runtime repositories into the upgraded database.
Can anyone please suggest whether this is happening due to version incompatability?
or is there any patches/scripts that needs to be run after the database upgradation?
Thanks in advance.

Hi there,
I upgradet a cuple of Times a Database
and use the OWB (and the Workflow) after that again.
I didn´t know exactly what´s going on by you
but maybe after the Upgrade there´re no more OWB Informations in teh Schemata?
You can start the Design Browser (ControlCenter), right?
Question: Is the DesignRepository in the same Instance
as the Runtime Repository?
If not, then i think it´s the best Way to reinstall the OWB Components using the Runtime Wizzards (runtimeinst.sh under UNIX).
If it is the same Instance try to take a look in the Log-Files from the Upgradeprocess.
You can even try to view the Oracle Documentations
about what´s exactly happened during the Upgrade.
Sorry, i think that didn´t help you very much, but i think at least with a new Installation of the OWB Components you can sure to fix your Problem.
Regards
Lone

Repeated Corruption of Spotlight Database on Time Machine disk?

I'm going to try this here since I don't seem to get much traction with this question in the Time Machine forum, and there is no forum here specific to Spotlight issues in Leopard:
I've been seeing repeated corruption of the Spotlight database on my external, Fireware 800, LaCie drive which is used exclusively for Time Machine. The symptom is that searches done in the Finder window after entering Time Machine produce no results or partial results.
There is no problem with Spotlight on the main hard drive for my laptop.
I received instructions from AppleCare for how to find and delete the hidden folder which makes up the Spotlight database on that drive -- an action which causes Spotlight to immediately rebuild the database on that drive from scratch -- but within days after doing that the database is corrupt again.
An additional symptom is that errors appear in the Console during a reboot -- but only if the Time Machine drive happens to be attached during the reboot. If the drive is attached AFTER booting and logging in, no such errors appear. The errors are from the "mds" process, and indicate either that a portion of the Spotlight database's "Stores" folder is having problems "storing dirty pages", and/or that a portion of the Spotlight database needs to be "recovered". Once those error messages start to appear, they will appear (identically) on every reboot where the drive is attached. No "recovery" happens. And searches after entering Time Machine fail to produce full results as described above.
There are no other Console complaints that appear relevant. No corrupt files during Time Machine backups, no errors when having entered Time Machine to view or restore files, no errors during searches themselves while in Time Machine.
Attempting to rebuild the Spotlight datbase on that drive by dragging it into the System Preferences > Spotlight > Privacy list and then removing it are fruitless. Spotlight indexing fires up for only a couple seconds after removing the disk from Privacy and there is no change in the search failures. And no new error message are entered in the Console. The same thing happens when attempting to use the "mdutil" command from Terminal to force a rebuild (as instructed by AppleCare). Only completely trashing the hidden Spotlight database folder on that drive suffices to get Spotlight to rebuild the database from scratch and start over in a fresh, uncorrupted state. But that doesn't last!
Meanwhile, Time Machine backups themselves are working just fine. No errors -- everything seems to be getting over to the drive -- and viewing within or restoring from Time Machine continues to work without problem. That is, the problem is entirely and ONLY within Spotlight for the Time Machine drive. (Again, that drive is used only for Time Machine.)
And as stated above, Spotlight continues to work without issue on the main hard drive.
Disk Utility > Verify Disk also has no complaints about that Time Machine drive (or the main hard drive)
And the usual panacea cures (booting once in Safe Mode, reset PRAM, reset PCU, Repair Permissions) also have no effect on this problem.
The computer in question was an "upgrade" install from 10.4.10 and has two accounts on it -- a non administrative account for normal work and an Administrator account that is almost never used. Only the one drive, the main hard drive, is being captured by the Time Machine backups. Nothing has been excluded from the Time Machine backups. I've even done a successful "full restore" of the system from that Time Machine. I.e., this is all very plain vanilla stuff. I can't fathom why I'm having this problem.
My Time Machine dates back to after installing 10.5.1. I've tried the process of deleting, and thus recreating, the Spotlight database several times without any luck.
Yesterday, after applying the "Time Machine and Airport Drivers" update to my 10.5.2 system, I decided it was time for a fresh start just in case there was something about the data put onto the drive by the older, 10.5.1, Time Machine that was causing Spotlight such grief.
So I erased the Time Machine drive and did an entirely new initial backup.
That completed without errors.
I then did a few incremental backups on top of that. After which I did a reboot to see if there were any Console error messages from mds. There were none, and my tests of searches while viewing in Time Machine all produced correct and complete results.
So far so good.
However, this morning, after I booted up with the Time Machine drive attached, I went immediately into Console and found the dreaded error messages from the mds process. And sure enough my searches inside of Time Machine now only produce partial results again. Here are the two messages I'm getting at the moment (with personal information "xxx"d out):
3/20/08 1:48:48 PM mds[26] (/Volumes/xxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/4CE0F19E-8757-43F1-A5DD-06B1DCAD0E50)(E rror) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 30
3/20/08 1:48:48 PM mds[26] (/Volumes/xxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/ABE285E8-4E3D-45BD-A3EF-D9A5B4A149DA)(E rror) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 30
So far I have NOT yet seen the messages saying that the Spotlight database "needs recovery".
I'm at a loss on this one. Again, the Time Machine backups themselves seem to be fully complete and fully functional. And Spotlight was perfectly happy after the new, initial backup, and a few incremental backups.
But I just can't get Spotlight to STAY happy with this Time Machine drive.
Any suggestions?
--Bob

OK I've completed the repartitioning test and the results are unexpected! Here's what I did and what I've spotted so far:
First, the only differences between what I'm going to list here and what I've done before is the repartitioning of the drive and the fact that I decided to do things this time entirely while logged in to my Administrator account. In the past, I did this stuff logged into my "standard" account and supplying Admin passwords when requested:
@ Rebooted with the drive attached and logged in to Admin
@ In System Preferences > Time Machine, did a Change Disk to No Disk to turn off Time Machine backups.
Note: In what follows, each of the several times Time Machine asked me if I wanted to use the external drive as the new Time Machine drive I selected "Cancel".
@ Used Disk Utility to re-partition the Time Machine drive into 2 untitled partitions (Apple Partition Map since this is a Powerbook Mac, Mac OS X Extended (Journalled) formatting, Mac OS 9 drivers turned off). I then partitioned it AGAIN back to 1 partition titled as my Time Machine drive (same settings). I did this two step process to make SURE the partitioning data was actually being re-written.
@ Used Disk Utility to Erase the single partition just created -- using the option to Write 0's to the drive to make sure all of the drive was exercised.
@ Checked and found the Time Machine volume was now identified as disk1s3.
@ Used Disk Utility to Verify Disk on my main hard drive.
@ Checked in Console after all of this and there were no I/O or other errors logged.
The next few steps were done to maximize the chances that my new "initial backup" would be as clean as possible.
@ Shut Down the computer and rebooted once into Safe Mode to let the Safe Mode boot delete caches and do its other background maintenance tasks. Shut Down immediately from the Safe Mode login window instead of logging in.
@ Rebooted while resetting PRAM. Just because.
@ Logged in as Admin, and used Disk Utility to Repair Permissions on the main hard drive. No messages were generated by this.
@ Rebooted once again and logged back in as Admin to get things into a fresh state.
At this point I was now ready to start the new, Time Machine "initial backup". However before I did that I decided to check the Console one more time.
Imagine my surprise when I found one each of the two Spotlight related error messages I reported above! There was one "needs recovery" error and one error trying to "store dirty pages"! (Note that normally I see TWO of each of these.)
Keep in mind that the drive had just been freshly partitioned and then erased again. Time Machine had never been given access to the drive. And no other user applications had been run. And yet the Spotlight database was ALREADY generating errors on that drive!
Upon checking further, I discovered that the first pair of these error messages was generated during the Safe Mode boot above. They were generated again during the boot where I reset PRAM.
BUT, there were NO ERROR MESSAGES in the most recent reboot I had just completed!
At this point I decided to do a 2 more reboots and there were NO ERROR MESSAGES in either of those.
Curious indeed! Well perhaps some sort of recovery had happened.
In any event, at this point I decide to do the "initial backup".
@ In System Preferences > Time Machine, I selected the drive for Time Machine use and let the initial backup complete. I also had Console running during this. The backup completed without any significant messages. In fact one additional incremental backup also completed without errors before I noticed it was done.
At this point, I entered Time Machine and tried my usual test searches which have demonstrated the Spotlight corruption in the past, and there were no problems. Spotlight was apparently good.
I then rebooted and checked the Console and son of a gun but the Spotlight error messages were back -- this time 2 of each.
However, when I checked searches in Time Machine -- THEY WORKED! This is the first time I've ever seen a case where the presence of those error messages during reboot wasn't accompanied by search failures inside of Time Machine.
I immediately did another reboot -- AND NO ERROR MESSAGES!
I've since done several additional incremental backups and several reboots, and I can't find a pattern anymore. The error messages OFTEN appear on reboot (if the Time Machine drive is attached), but not ALWAYS as was the case in the past. And up to now searches inside of Time Machine are working without problems.
I can see several possible explanations:
1) The error messages are spurious (or there is some sort of automatic recovery that is working now when it didn't work before) and the repartitioning above actually fixed the problem.
2) The database is indeed corrupted, but the corruption has moved to a portion of the database that my test searches aren't exercising.
3) I need to do more incremental backups before the database corruption will actually become visible in my test searches. I.e., the problem just hasn't had time to develop yet.
Meanwhile I heard back from LaCie support that they have not heard of a problem like this for Time Machine or Spotlight on this particular drive. I've also pointed them at this thread for details.
So I'll just continue to use this Mac normally over the next few days, while periodically checking to see if the Spotlight search failures reappear and to see if I can spot any pattern as to why those Console error messages sometimes appear on reboot and sometimes not.
I'll report back when I have more info.
Again, if anyone has any insight into what those 2 Console error messages actually mean, or if anyone else is seeing those error messages, or is having Spotlight search failures when inside Time Machine whether or not you see those error messages, please chime in.
--Bob

Database upgrade concepts

Hello,
Please help me understand the complete scenario on database upgrade, here is what I know:
- We have Oracle 9i database installed
- We install new Oracle 10g Database on same machine with different SID
- We upgrade Oracle 9i database using DBUA of Oracle 10g
- The Oracle 9i database is upgraded to Oracle 10g Database and we dont need to move our data from old database to any new place
1. What happens to the new Oracle 10g installation ? Should we remove the installation ?
2. Will the SID of old home be changed or will it be the same?
I read many docs, all of them explain the method to upgrade, but not the complete scenario.
Thanks in advance :)

- We have Oracle 9i database installedOK
- We install new Oracle 10g Database on same machine
with different SIDNo. A SID is associated with a database. if you're going to use the DBUA, you'd just want to install the 10g software into a separate Oracle Home. You would not want to create a new database.
- We upgrade Oracle 9i database using DBUA of Oracle
10gOK
- The Oracle 9i database is upgraded to Oracle 10g
Database and we dont need to move our data from old
database to any new placeCorrect
1. What happens to the new Oracle 10g installation ?
Should we remove the installation ?No. The 10g Oracle Home you just created is the new Oracle Home for your database.
2. Will the SID of old home be changed or will it be
the same?I'm not sure what you're asking here, but I suspect the question is moot based on the corrections above.
Of course, I assume that you'll be upgrading your dev & test databases long before you try to upgrade prod so you'll have plenty of practice and plenty of time to make sure that everything is working after the upgrade as you'd expect...
Justin

Forms HOST command no longer works after database upgrade from 10g to 11g

Hi,
After upgrading the database 10g to 11g the forms HOST command no longer works on Unix server. The form used to work fine prior the upgrade. I read all the threads I could find and did not see any solutions. Adding PATH and LD_LIBRARY_PATH does not work because it does not even run a basic shell script. (I saw this solution, adding PATH and LD_LIBRARY_PATH, in many questions / threads).
1. I wouldn't expect the database upgrade to be an issue, but it is the only change we had.
2. Note, 11g is Oracle Fusion Middleware which is quite a bit different than 10g.
I even tried the most basic commands like "echo" which is a build-in Unix command and there is no directory for it (ie. no /usr/bin - so variable PATH is irrelvent). i.e HOST('echo hi'); and HOST('echo "hi" '); and even HOST ('echo hi > /my_file.txt'); all returns FORMS_FAILURE (actually the if is IF FORM_SUCCESS THEN ... else ... and the else part always runs now - whereas it didn't before.).
Or basic commands like /usr/bin/ls as in HOST(/usr/bin/ls). At that point I was just testing the Unix command would return FORM_SUCCESS even though I could not see the results (because they weren't writing to a log file). Notice that I'm using the direct path /usr/bin so no Unix environment variables were needed.
The form does use webutil but that part works. For example, we have webutil_file_transfer( ....) The file shows up on the application server and in the expected directory.
Here's the main goal. Upload a file from clients local PC to the datebase server. The form uploads the file to the Application server, then we have a Unix script to scp (secure copy) the file from the application server to the database server. IF webutil, or any other Oracle functions could put the file on the database server that would be better. But, I don't know of any procedures that do that - or would have done it cleanly (i.e. storing to database and write back to server and then using a blob etc. )
Anyway, I was hoping someone would help with either of these.
1) Get the HOST command to work. - If we can get that to work then I wouldn't need any more help. We can just call the already existing Unix script to copy the file from the application server to the database.
2) OR be able to upload directly to the database server - wanted to do that originally
Any help would be appreciated

Solution for those interested and for anyone else searching this forum for a solution
I found this on My Oracle Support:
<h3>Host Command from Forms Not Working in 11g in Sun Solaris Sparc OS [ID 1157346.1]</h3>
Applies To: Oracle Forms - Version 11.1.1.1.0 and later
Sun SPARC Sun OS
Symptoms:
When trying to execute a Shell script or any OS command using the host() Built-in from Forms 11g, the host()command is not getting executed. The same functionality works on other operating systems and in previous versions like 10gR2.
Steps to be followed:
1) Take a backup and edit the $DOMAIN_HOME/config/fmwconfig/servers/WLS_FORMS/applications/formsapp_11.1.1/config/default.env or any custom environment file.
2) Locate the following environment variable:
LD_PRELOAD=/ora10gas/app/11.1.0/Middleware/as_1/jdk/jre/lib/sparcv9/libjsig.so
3) Comment out this variable. After the changes, it will look like the following:
#LD_PRELOAD=/ora10gas/app/11.1.0/Middleware/as_1/jdk/jre/lib/sparcv9/libjsig.so
3) a) Instead of LD_PRELOAD, kindly use LD_PRELOAD_64 as given below :
LD_PRELOAD_64=/ora10gas/app/11.1.0/Middleware/as_1/jdk/jre/lib/sparcv9/libjsig.so
(This makes HOST AND RUN_REPORT_OBJECT work fine).
4) Save the file and execute your forms. The Host() built-in will work as expected
The LD_PRELOAD setting in default.env is only required for the working of signal chaining facility in JVM version 1.5 and later. If you are not using theSignal chaining facility, this variable is not required. For more information, refer to the following documentation
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e14772/forms.htm#CJAJGAFF

Oracle Database upgrade to 11G (Host_Command Issues)

Sorry I'm posting this again. Original post in Database - Upgrade. I'm not getting a lot of clicks in that category
We recently upgraded to Oracle 11g (Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production). Our PL/SQL release: (PL/SQL Release 11.2.0.2.0 - Production). We use a lot of host commands inside our PL/SQL stored procedures. One of these included fetching data from an external server and pushing the data into Oracle Tables.
Most of this process is running fine, except the execution never completes. There is no issue data wise. It's just that the Host_command doesn't receive the completion status and seems to be running even though there's nothing going on in the background.
The Oracle e-business suite's concurrent program based on this stored proc also never completes, though it doesn't do anything in the background. For testing purpose, our DBA used 2 insert statements one before and one after the host_command. The insert before the host_command worked but not the one after. Please help! This is happening after we upgraded to 11g 3 weeks ago!
Thanks, Naveen Gagadam.

Pl do not post duplicates - Upgrade to 11g, Host Command Inside Stored Proc doesn't end.
I have moved your duplicate post to the EBS forums
Srini

Database Upgradation from oracle 9.2.0.8 to oracle11gR2

Hi
we are using AIX 5.3 TL 10 SP4 and we are upgrading DB from oracle9.2.0.8 to oracle 11.2.0.2
i am having some doubt from below pre-upgrade scripts out put.
oratst@ebsdevdb on /tmp # sqlplus "/as sysdba"
SQL*Plus: Release 9.2.0.8.0 - Production on Mon Jul 4 10:11:48 2011
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
SQL> spool 11202_upgrade.txt
SQL> @utlu112i.sql
Oracle Database 11.2 Pre-Upgrade Information Tool 07-04-2011 10:17:06
Script Version: 11.2.0.2.0 Build: 001
Database:
--> name: EBSTEST
--> version: 9.2.0.8.0
--> compatible: 9.2.0
--> blocksize: 8192
--> timezone file: V1
Logfiles: [make adjustments in the current environment]
--> The existing log files are adequate. No changes are required.
Tablespaces: [make adjustments in the current environment]
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
--> TOOLS tablespace is adequate for the upgrade.
.... minimum required size: 8 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 61 MB
--> AR_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 33497 MB
--> FND_TABLE tablespace is adequate for the upgrade.
.... minimum required size: 45447 MB
--> AMVD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> ASOD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> CCTD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> IBUD tablespace is adequate for the upgrade.
.... minimum required size: 1 MB
--> IEMD tablespace is adequate for the upgrade.
.... minimum required size: 5 MB
--> IEOD tablespace is adequate for the upgrade.
.... minimum required size: 4 MB
--> JTFD tablespace is adequate for the upgrade.
.... minimum required size: 135 MB
--> OKCD tablespace is adequate for the upgrade.
.... minimum required size: 34 MB
--> XDPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> XNPD tablespace is adequate for the upgrade.
.... minimum required size: 7 MB
--> APPS_UNDOTS1 tablespace is adequate for the upgrade.
.... minimum required size: 849 MB
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Note: Pre-upgrade tool was run on a lower version 64-bit database.
--> If Target Oracle is 32-Bit, refer here for Update Parameters:
WARNING: --> "compatible" must be set to at least 10.1.0
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
WARNING: --> "compatible" must be set to at least 10.1.0
WARNING: --> "shared_pool_size" needs to be increased to at least 532 MB
WARNING: --> "java_pool_size" needs to be increased to at least 128 MB
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
-- No renamed parameters found. No changes are required.
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
--> optimizer_max_permutations 10.1 OBSOLETE
--> row_locking 10.1 OBSOLETE
--> undo_suppress_errors 10.1 OBSOLETE
--> max_enabled_roles 10.1 DEPRECATED
--> enqueue_resources 10.2 OBSOLETE
--> sql_trace 10.2 DEPRECATED
--> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
--> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"
Components: [The following database components will be upgraded or installed]
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Real Application Clusters [upgrade] INVALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [install]
--> Oracle Java Packages [upgrade] VALID
--> Oracle interMedia [upgrade] VALID
--> Spatial [upgrade] VALID
Miscellaneous Warnings
WARNING: --> Passwords exist in some database links.
.... Passwords will be encrypted during the upgrade.
.... Downgrade of database links with passwords is not supported.
WARNING: --> Deprecated CONNECT role granted to some user/roles.
.... CONNECT role after upgrade has only CREATE SESSION privilege.
WARNING: --> Database is using a timezone file older than version 14.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 9.2.0.8.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Database contains INVALID objects prior to upgrade.
.... The list of invalid SYS/SYSTEM objects was written to
.... registry$sys_inv_objs.
.... The list of non-SYS/SYSTEM objects was written to
.... registry$nonsys_inv_objs.
.... Use utluiobj.sql after the upgrade to identify any new invalid
.... objects due to the upgrade.
.... USER ADWANIAH has 1 INVALID objects.
.... USER APPS has 34 INVALID objects.
.... USER CHAKKACHANSA has 1 INVALID objects.
.... USER FA_USER has 9 INVALID objects.
.... USER SYSSEL has 2 INVALID objects.
.... USER SYSTEM has 30 INVALID objects.
.... USER XXITDFINAD has 7 INVALID objects.
WARNING: --> SYSTEM schema default tablespace has been altered.
.... The SYSTEM schema default tablespace is currently set to TOOLS.
.... Prior to upgrading your database please reset the
.... SYSTEM schema default tablespace to SYSTEM using the command:
.... ALTER USER SYSTEM DEFAULT TABLESPACE SYSTEM;
WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
Recommendations
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following commands
while connected as SYSDBA:
EXECUTE dbms_stats.gather_schema_stats('CTXSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('DBSNMP',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('MDSYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDPLUGINS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('ORDSYS',options=>'GATHER'
estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('OUTLN',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYS',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
EXECUTE dbms_stats.gather_schema_stats('SYSTEM',options=>'GATHER'
,estimate_percent=>DBMS_STATS.AUTO_SAMPLE_SIZE
,method_opt=>'FOR ALL COLUMNS SIZE AUTO'
,cascade=>TRUE);
Oracle recommends removing all hidden parameters prior to upgrading.
To view existing hidden parameters execute the following command
while connected AS SYSDBA:
SELECT name,description from SYS.V$PARAMETER WHERE name
LIKE '\_%' ESCAPE '\'
Changes will need to be made in the init.ora or spfile.
Oracle recommends reviewing any defined events prior to upgrading.
Changes will need to be made in the init.ora or spfile.
Oracle recommends reviewing any defined events prior to upgrading.
To view existing non-default events execute the following commands
while connected AS SYSDBA:
Events:
SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
WHERE UPPER(name) ='EVENT' AND isdefault='FALSE'
Trace Events:
SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2
WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'
Changes will need to be made in the init.ora or spfile.
SYSAUX Tablespace:
[Create tablespace in the Oracle Database 11.2 environment]
--> New "SYSAUX" tablespace
.... minimum required size for database upgrade: 500 MB
From above output script
1)SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 8546 MB
From system tablespace minimum required size means free space from system tablespace or total size of system tablespace?
i am going to use dbua utility for upgrade means does it alter tablespace as per output of scripts or we need to manually alter tablespace size as per requirement?
2)WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
what is above warning and how can i configure ACL's for APPS User?
Thanks
With Regards
A-Z

Hi
oratst@ebsdevdb on /ebdbh/11g/data/cfgtoollogs/dbua/ebstest/upgrade1 # more Upgrade_Directive.log
Connected.
ODMA_DIRECTIVE:VERSION:9.2.0.8
ODMA_DIRECTIVE:MIGRATE_SID:
ODMA_DIRECTIVE:ORA:IGNORE:06512:
ODMA_DIRECTIVE:ORA:FATAL:00600:
ODMA_DIRECTIVE:ORA:FATAL:01012:
ODMA_DIRECTIVE:ORA:FATAL:01031:
ODMA_DIRECTIVE:ORA:FATAL:01034:
ODMA_DIRECTIVE:ORA:FATAL:01078:
ODMA_DIRECTIVE:ORA:FATAL:01092:
ODMA_DIRECTIVE:ORA:FATAL:01109:
ODMA_DIRECTIVE:ORA:FATAL:01119:
ODMA_DIRECTIVE:ORA:FATAL:01507:
ODMA_DIRECTIVE:ORA:FATAL:01722:
ODMA_DIRECTIVE:ORA:FATAL:03113:
ODMA_DIRECTIVE:ORA:FATAL:03114:
ODMA_DIRECTIVE:ORA:FATAL:07445:
ODMA_DIRECTIVE:ORA:FATAL:12560:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01650:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01651:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01652:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01653:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01654:
ODMA_DIRECTIVE:ORA:RECOVER_TBS:01655:
ODMA_DIRECTIVE:ORA:RECOVER_ROLL:01562:
ODMA_DIRECTIVE:ORA:RECOVER_INIT:04031:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catupgrd.sql:
ODMA_DIRECTIVE:BOUNCE_DATABASE:UPGRADE:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:rdbms/admin/catuppst.sql:
ODMA_DIRECTIVE:SCRIPT:UPGRADE:sqlplus/admin/help/hlpbld.sql helpus.sql:
Thanks
With Regards
A-Z

Firmware upgrade times out (BEFW11S4 v4)

Hi, my firmware upgrade times out everytime and i've read that the only way to get past this is by flash-upgrading the router through this web address ftp.linksys.com/pub/network but the link doesn't work for me and says '550 failed to change directory'. Is there another link i can try or another solution?
Previous thread: http://forums.linksysbycisco.com/linksys/board/message?board.id=Wireless_Routers&thread.id=122275

Download Firmware 314 KB...
Download TFTP Utility...
After downloading the Firmware rename the file(like - befw11s4)...
Follow these steps to upgrade the firmware on the device : -
Double click the TFTP.exe file and click run.
For Server- Enter the IP Address of the router that you assigned. By default, the router is 192.168.1.1...
For Password- Enter the password you assigned the router. By default, the router’s password is “admin”.
For File- Click the triple “…” button and browse for the .bin firmware file...
Click Upgrade button to start upgrading. A progress bar should show up to show the progress.
Once the Upgrade is done press and hold the reset button for 30 seconds...Release the reset button...Unplug the power cable from your router, wait for 30 seconds and re-connect the power cable...Now re-configure your router...

Database upgrade time.

Similar Messages

Maybe you are looking for