Dbua error wile upgrade from 9.5.0.5 to 10.2.0.4

Question

I am upgrading from 9.2.0.5 to 10.2.0.4
i earlier tried to upgrade from 9.2.0.5 to 10.2.0.3, however it failed because of not applying patch-
i then cloned the instance and installed 10g software,companion products,10.2.0.4. patchset. however when u run dbua it gives a weird error->
ora 1507---database not mounted
dbua thinks this is rerun and is trying to connect to the database with orcle home"/u08/fadevdb/10g". If you beleive this is not a rerun, remove below file and rerun DBUA again
/u08/fadevdb/10g/cfgtoollogs/dbua/logs/Welcome_FADEV.tct"
However /u08/fadevdb/10g/cfgtoollogs/dbua/logs/Welcome_FADEV.txt" files does not exist
I checked the alert log
Additional information: 4087
Fri Dec 19 23:00:24 2008
ORA-205 signalled during: ALTER DATABASE MOUNT...
Fri Dec 19 23:43:40 2008
Beginning log switch checkpoint up to RBA http://0x2e.2.10, SCN: 0x0000.88b18ab0
Thread 1 advanced to log sequence 46
Current log# 1 seq# 46 mem# 0: /u04/fadevdata/log01a.dbf
Current log# 1 seq# 46 mem# 1: /u06/fadevdata/log1b.dbf
Sat Dec 20 00:04:22 2008
Completed checkpoint up to RBA http://0x2e.2.10, SCN: 0x0000.88b18ab0
^C$ tail -100 alert_FADEV.log
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Shared memory segment for instance monitoring created
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /u08/fadevdb/10g/dbs/arch
Autotune of undo retention is turned on.
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
tracefiles_public = TRUE
processes = 200
sessions = 400
timed_statistics = TRUE
shared_pool_size = 301989888
large_pool_size = 8388608
java_pool_size = 54525952
streams_pool_size = 50331648
shared_pool_reserved_size= 30000000
sharedpool_reserved_min_alloc= 4100
nls_language = american
nls_territory = america
nls_sort = binary
nls_date_format = DD-MON-RR
nls_numeric_characters = .,
nls_comp = binary
nls_length_semantics = BYTE
control_files = /u04/fadevdata/cntrl01.dbf, /u06/fadevdata/cntrl02.dbf, /u03/fadevdata/cntrl03.dbf
db_block_checksum = TRUE
db_block_size = 8192
db_cache_size = 163577856
compatible = 9.2.0
log_buffer = 14282752
log_checkpoint_interval = 100000
log_checkpoint_timeout = 1200
db_files = 512
db_file_multiblock_read_count= 8
log_checkpoints_to_alert = TRUE
dml_locks = 10000
undo_management = AUTO
undo_tablespace = APPS_UNDOTS1
undo_retention = 1800
db_block_checking = FALSE
O7_DICTIONARY_ACCESSIBILITY= FALSE
session_cached_cursors = 200
utl_file_dir = /usr/tmp, /usr/tmp, /u02/fadevdb/9.2.0/appsutil/outbound/FADEV_fadevdb, /usr/tmp
job_queue_processes = 2
systemtrig_enabled = TRUE
cursor_sharing = EXACT
parallel_min_servers = 0
parallel_max_servers = 8
background_dump_dest = /u02/fadevdb/9.2.0/admin/FADEV_fadevdb/bdump
user_dump_dest = /u02/fadevdb/9.2.0/admin/FADEV_fadevdb/udump
max_dump_file_size = 20480
core_dump_dest = /u02/fadevdb/9.2.0/admin/FADEV_fadevdb/cdump
session_max_open_files = 20
optimizer_features_enable= 9.2.0
db_name = FADEV
open_cursors = 600
ifile = /u02/fadevdb/9.2.0/dbs/FADEV_fadevdb_ifile.ora
sortelimination_cost_ratio= 5
btree_bitmap_plans = FALSE
fastfull_scan_enabled = FALSE
query_rewrite_enabled = true
indexjoin_enabled = FALSE
sqlexecprogression_cost= 2147483647
likewith_bind_as_equality= TRUE
pga_aggregate_target = 1073741824
workarea_size_policy = AUTO
aq_tm_processes = 1
olap_page_pool_size = 4194304
PSP0 started with pid=3, OS id=28588
MMAN started with pid=4, OS id=28590
PMON started with pid=2, OS id=28586
DBW0 started with pid=5, OS id=28592
LGWR started with pid=6, OS id=28594
CKPT started with pid=7, OS id=28596
SMON started with pid=8, OS id=28598
RECO started with pid=9, OS id=28600
CJQ0 started with pid=10, OS id=28602
MMON started with pid=11, OS id=28604
MMNL started with pid=12, OS id=28606
Fri Dec 19 23:00:21 2008
ALTER DATABASE MOUNT
Fri Dec 19 23:00:21 2008
ORA-00202: control file: '/u04/fadevdata/cntrl01.dbf'
ORA-27086: unable to lock file - already in use
SVR4 Error: 11: Resource temporarily unavailable
Additional information: 8
Additional information: 4087
Fri Dec 19 23:00:24 2008
ORA-205 signalled during: ALTER DATABASE MOUNT...
Fri Dec 19 23:43:40 2008
Beginning log switch checkpoint up to RBA http://0x2e.2.10, SCN: 0x0000.88b18ab0
Thread 1 advanced to log sequence 46
Current log# 1 seq# 46 mem# 0: /u04/fadevdata/log01a.dbf
Current log# 1 seq# 46 mem# 1: /u06/fadevdata/log1b.dbf
Sat Dec 20 00:04:22 2008
Completed checkpoint up to RBA http://0x2e.2.10, SCN: 0x0000.88b18ab0
I then found that ctr101.dbf had permissions of "rw-r-r". I gave 777 permission.aborted dbua and again started dbua. However it still gives the same problem.
If you note the alert log...then 10g is trying to start while 9i is already running.i then shutdown and started 9i again and then started dbua...however it again gives the same error.
How do i resolve it?

Answer 1

Hi,
I would quickly identify some of the errors that I'm seeing in the log:
ORA-01034: ORACLE not available
This is probably occuring due to invalid entries in /etc/oratab and /var/opt/oracle/oratab, where ORACLE_HOME and ORACLE_SID are not properly defined. This could also be due to invalid entries within the listener file. Further to this, you may try to read through the following Metalink Note to resolve this issue:
https://metalink.oracle.com/metalink/plsql/f?p=130:14:2840960078839325001::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,302510.1,1,1,1,helvetica
A similar issue is being discussed here ORA-27086: unable to lock file over NFS -- but it's NOT Netapp!
SVR4 Error: 11: Resource temporarily unavailable
This is probably over-writing some already existing/production control files. Try pointing CONTROL_FILES parameter within init.ora to point to a new location. Once this is done you must now change the location of your datafiles, and finally change the location of your redo log files.
ORA-205 signalled during: ALTER DATABASE MOUNT
This again is falling in succession to the errors being popped up against the control files. Try to start the database without mounting it and check for the control files in v$parameter2.
Lastly, you may also want to check if the database is starting from the spfile instead of the pfile. If it is, alter it to start from the pfile.
I hope this helps.
Regards,
Naveed.