DBCA failing after 10.2.03 upgrade
Mike Jones
to use DBCA to create a new database. I believe the problem is the
10.2.0.3.0 patch set does not upgrade the seed database used by DBCA from
10.2.0.1.0 to 10.2.0.3.0. Thus after DBCA completes the DB replication and
attempts to start the instance it fails with a disconnect (essentially the
same error one receives if they do not upgrade their current databases after
the patch installation). This behavior is understandable given it's
attempting to start a 10.2.0.1.0 instance. My question is how can I update
the seed database or otherwise utilize DBCA to create new databases after an
upgrade?
I am running Oracle 10g 10.2.0.1.0 with the 10.2.0.3.0 patch upgrade, Oracle
Enterprise Linux 4 Update 6 (x86, 32 bit, Oracles version of Linux). I've
used DBUA and/or catupgrd.sql to upgrade my existing databases without
problem. I've read the release notes, performed the necessary pre/post
installation tasks, etc. I can't seem to find any reference to this issue
through Google or in these forums. Am I the only one experiencing this
problem?
Thanks in advance
DA Morgan
The only one I know. <g>
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damo...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
Maxim Demenko
I suggest, you should investigate the upgrade log file to find out, why
your seed databases were not patched. In addition Note 556639.1 may be
helpful.
Best regards
Maxim
Mike Jones
"Maxim Demenko" <mdem...@gmail.com> wrote in message
news:48136080...@gmail.com...
Thanks Maxim. I have reviewed the installation log files and did not see
anything about a failure to install the seed database files. Is there
something specific I should be looking for? One thing to note from the log
file are a number of the following entries:
INFO: OUI-10070:The patch oracle.client 10.2.0.3.0, which is part of patch
set Oracle Database 10g Release 2 Patch Set 2 10.2.0.3.0 , has not been
selected for installation.
Perhaps the seed database is part of something I have not selected (though I
don't recall being given the option to select anything)?
The article was helpful and after manually copying the seed database files
to the Oracle installation I am now able to use DBCA to create databases.
However I did check the permissions on the seed database files and the
parent (templates) directory and the OS permissions do allow the oracle user
to replace the files in question (I copied the new files from the patch DVD
as the oracle user and did not experience any problems).
I find it odd that I am the only person (so it seems) to have encountered
this problem. I've encountered it on three different systems. I've used
three different 10.2.0.3.0 patch downloads. The only thing common between
them all is the original DB (10.2.0.1.0) installation media. Perhaps I'll
download it again and give it another try.
Anyway I do have a work around (now that I know where the seed database
files are stored on the 10.2.0.3.0 patch DVD) that allows me to proceed but
I would like to figure out what the root cause of this problem is.
hpuxrac
snip
1) Can you in your environment create a reproducible test case? If so
great otherwise my guess is that you possibly did something unusual
somewhere along the way. The OUI error messages should mean
something ...
2) Did you try using the 10.2.0.4 patchset which should be available
for your environment by now? In other words, why patch to 10.2.0.3
when oracle has a newer patchset available now?
Mike Jones
> news:2a57619b-45a3-4833...@e39g2000hsf.googlegroups.com...
> On Apr 26, 5:07 pm, "Mike Jones" <mj20...@hotmail.com> wrote:
>
> snip
>
> 1) Can you in your environment create a reproducible test case? If so
> great otherwise my guess is that you possibly did something unusual
> somewhere along the way. The OUI error messages should mean
> something ...
I have been able to reproduce the problem on three different systems and
repeated installs on a test system. It's very repeatable for me. Am I to
assume this repeatable behavior is limited to myself? I was unable to find
any references to this problem when doing my research.
> 2) Did you try using the 10.2.0.4 patchset which should be available
> for your environment by now? In other words, why patch to 10.2.0.3
> when oracle has a newer patchset available now?
I am downloading 10.2.0.4.0 right now. I'll post my results here.
hpuxrac
snip
> > 1) Can you in your environment create a reproducible test case? If so
> > great otherwise my guess is that you possibly did something unusual
> > somewhere along the way. The OUI error messages should mean
> > something ...
>
> I have been able to reproduce the problem on three different systems and
> repeated installs on a test system. It's very repeatable for me. Am I to
> assume this repeatable behavior is limited to myself? I was unable to find
> any references to this problem when doing my research.
Sounds likely then that you will be able to submit a service request
that oracle might actually be able to reproduce your results and file
a bug for. Well then of course there's always that fix status "in next
release" that doesn't make any of us very satisfied.
I for one have not used dbca for anything over the last 5 years for
anything but a "custom" database where oracle rebuilds everything from
scratch. Still there are enough oracle users out there on that this
sure looks like it should have been discovered and reported already.
Or all the 32 bit linux users still on base 10.2? Doesn't sound very
likely to me.
Filing a service request looks unavoidable.
>
> > 2) Did you try using the 10.2.0.4 patchset which should be available
> > for your environment by now? In other words, why patch to 10.2.0.3
> > when oracle has a newer patchset available now?
>
> I am downloading 10.2.0.4.0 right now. I'll post my results here.
Keep us posted.
Mike Jones
On Apr 26, 6:18 pm, "Mike Jones" <mj20...@hotmail.com> wrote:
snip
>> > 1) Can you in your environment create a reproducible test case? If so
>> > great otherwise my guess is that you possibly did something unusual
>> > somewhere along the way. The OUI error messages should mean
>> > something ...
>>
>> I have been able to reproduce the problem on three different systems and
>> repeated installs on a test system. It's very repeatable for me. Am I to
>> assume this repeatable behavior is limited to myself? I was unable to
>> find
>> any references to this problem when doing my research.
>
> Sounds likely then that you will be able to submit a service request
> that oracle might actually be able to reproduce your results and file
> a bug for. Well then of course there's always that fix status "in next
> release" that doesn't make any of us very satisfied.
>
> I for one have not used dbca for anything over the last 5 years for
> anything but a "custom" database where oracle rebuilds everything from
> scratch. Still there are enough oracle users out there on that this
> sure looks like it should have been discovered and reported already.
> Or all the 32 bit linux users still on base 10.2? Doesn't sound very
> likely to me.
>
> Filing a service request looks unavoidable.
It's odd that I can reproduce it on three completely different systems. The
only thing in common between the three is the base (10.2.0.1.0) installation
media. I think I will try downloading it again and seeing if I can repeat
it. I'm surprised that I've been able to repeat it consistently (every one
has always done this) yet I haven't been able to find any postings of anyone
else experiencing the problem.
>> > 2) Did you try using the 10.2.0.4 patchset which should be available
>> > for your environment by now? In other words, why patch to 10.2.0.3
>> > when oracle has a newer patchset available now?
>>
>> I am downloading 10.2.0.4.0 right now. I'll post my results here.
>
> Keep us posted.
I have the same problem with the 10.2.0.4.0 patch set. Thanks for all your
assistance. I'll post back here once I've downloaded the base package. I
might also try it with a different OS (Solaris).
Frank van Bortel
> After upgrading from Oracle 10g 10.2.0.1.0 to 10.2.0.3.0 I am no longer
> able to use DBCA to create a new database. I believe the problem is the
> 10.2.0.3.0 patch set does not upgrade the seed database used by DBCA
> from 10.2.0.1.0 to 10.2.0.3.0.
Again? Oracle failed to do so with some 9i release, too. You'd
suspect some kind of learning mechanism...
Thus after DBCA completes the DB
> replication and attempts to start the instance it fails with a
> disconnect (essentially the same error one receives if they do not
> upgrade their current databases after the patch installation). This
> behavior is understandable given it's attempting to start a 10.2.0.1.0
> instance. My question is how can I update the seed database or otherwise
> utilize DBCA to create new databases after an upgrade?
The way you demonstrate to be familiar with below, plus the following:
- install the base line
- install all pre-seeded db instance flavors you want
- upgrade software plus instances
- save upgraded instances 'as template'
One reason I don't like seed databases; the other one
being the increased download time - a couple of scripts
would speed up the total installing process more than
this seed db stuff.
FvB
Maxim Demenko
Just installed a fresh 10.2.0.1 on CentOS 5.1 - with base package
downloaded from OTN, then patched to 10.2.0.4 - it appears, seed
database is replaced by patchset.
after base install:
oracle@col-co5-01:/opt/oracle/product/10gR2/assistants/dbca/templates >ll
total 112120
-rw-r----- 1 oracle dba 5728 Jun 30 2005 Data_Warehouse.dbc
-rwxr-xr-x 1 oracle dba 13017088 Jul 2 2005 example01.dfb
-rwxr-xr-x 1 oracle dba 991232 Jul 2 2005 example.dmp
-rw-r----- 1 oracle dba 5608 Jun 30 2005 General_Purpose.dbc
-rw-r----- 1 oracle dba 12050 May 16 2005 New_Database.dbt
-rwxr-xr-x 1 oracle dba 7061504 Jul 2 2005 Seed_Database.ctl
-rwxr-xr-x 1 oracle dba 93569024 Jul 2 2005 Seed_Database.dfb
-rw-r----- 1 oracle dba 5665 Jun 30 2005 Transaction_Processing.dbc
oracle@col-co5-01:/opt/oracle/product/10gR2/assistants/dbca/templates
>sha1sum Seed_Database.dfb
249727a3d7b1eca3f07cf5cf2806175e55e0436f Seed_Database.dfb
after patchset:
oracle@col-co5-01:/opt/oracle/product/10gR2/assistants/dbca/templates >ll
total 114104
-rw-r--r-- 1 oracle dba 5728 Feb 17 02:30 Data_Warehouse.dbc
-rw-r--r-- 1 oracle dba 13017088 Feb 17 11:33 example01.dfb
-rw-r--r-- 1 oracle dba 1048576 Feb 17 11:33 example.dmp
-rw-r--r-- 1 oracle dba 5608 Feb 17 02:30 General_Purpose.dbc
-rw-r--r-- 1 oracle dba 12050 Aug 18 2006 New_Database.dbt
-rw-r--r-- 1 oracle dba 7061504 Feb 17 11:30 Seed_Database.ctl
-rw-r--r-- 1 oracle dba 95543296 Feb 17 11:30 Seed_Database.dfb
-rw-r--r-- 1 oracle dba 5665 Feb 17 02:30 Transaction_Processing.dbc
oracle@col-co5-01:/opt/oracle/product/10gR2/assistants/dbca/templates
>sha1sum Seed_Database.dfb
df4a42c661f9fc02aec073060a72f91afd7b5121 Seed_Database.dfb
Maybe you should try indeed with another installation media.
Best regards
Maxim
Mike Jones
I've found the root cause of the problem. It turns out the file permissions
on Seed_Database.ctl and Seed_Database.dfb were incorrect. They were set
to -r-xr-xr-x on install instead of -rwxr-x-r-x. I am not sure how I missed
this the first time I checked them. I suspect the oversight was due to the
fact I checked them after I had manually copied the new seed files from the
10.2.0.3.0 upgrade media into the Oracle home. After performing a fresh
install of 10.2.0.1.0, changing the file permissions to -rwxr-x-r-x, and
upgrading to 10.2.0.3.0 I was able to use DBCA to create new databases.
I also downloaded another copy of 10.2.0.1.0 and installed from this new
download and everything went fine. So in conclusion it looks as if the
original media I was using has the incorrect permissions problem.
Now I have to decide if I should reinstall the two non-test database
installations from the good media. Who knows what else might be messed up
with those installations.
Thanks for everyone's assistance in this matter.