Home » RDBMS Server » Server Administration » STARTUP UPGRADE results in error ORA-01157: cannot identify/lock data (sun solaris 64 bit, 9i to 10g)
STARTUP UPGRADE results in error ORA-01157: cannot identify/lock data [message #303577] Fri, 29 February 2008 20:48 Go to next message
geeklol
Messages: 59
Registered: March 2005
Member
i am trying to upgrade 9.2.0 to 10.2.0 on sun solaris 64 bit mc.
i made changes to the init file, the init file now looks as below.
then when i try to startup the instance using startup upgrade, i get the error: I haven't changed anything and all worked fine in 9i. what's going on?

SQL> startup UPGRADE pfile=/usr/local/oracle/10.2.0/dbs/initlcectest.ora
ORACLE instance started.

Total System Global Area 1526726656 bytes
Fixed Size 1978848 bytes
Variable Size 452988448 bytes
Database Buffers 1056964608 bytes
Redo Buffers 14794752 bytes
Database mounted.
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '/db02/oradata/lcectest/data/system01.dbf'

-------------------------------------------------------------
init file for 10g,
##log_archive_start=true
log_archive_dest_1='LOCATION=/db01/redo/oradata/lcectest/arch/'
log_archive_format=arch_%t_%s_%r.arc
log_archive_dest_state_1 = enable

db_block_size=8192
db_cache_size=1000m
db_file_multiblock_read_count=16

open_cursors=300

db_domain=""
db_name=lcectest

background_dump_dest=/usr/local/oracle/admin/lcectest/bdump
core_dump_dest=/usr/local/oracle/admin/lcectest/cdump
timed_statistics=TRUE
user_dump_dest=/usr/local/oracle/admin/lcectest/udump

control_files=("/db01/redo/oradata/lcectest/control/control01.ctl","/db01/redo2/oradata/lcectest/control/control02.ctl")

session_max_open_files=20
compatible=10.2.0
streams_pool_size=50331648

instance_name=lcectest

job_queue_processes=10

aq_tm_processes=1
##compatible=9.2.0.0.0

##hash_join_enabled=TRUE
query_rewrite_enabled=FALSE
star_transformation_enabled=FALSE

java_pool_size=150m
large_pool_size=50m
shared_pool_size=150m

processes=500

fast_start_mttr_target=300

remote_login_passwordfile=EXCLUSIVE

pga_aggregate_target=100m
workarea_size_policy='auto'

undo_management=AUTO
undo_retention=10800
undo_tablespace=UNDO1
##log_parallelism=1
parallel_max_servers=9
Re: STARTUP UPGRADE results in error ORA-01157: cannot identify/lock data [message #303594 is a reply to message #303577] Fri, 29 February 2008 23:59 Go to previous message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

ORA-01157: cannot identify/lock data file string - see DBWR trace file

Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified.

Action: Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES
Previous Topic: Changing homes
Next Topic: ORA-01034: ORACLE not available and ORA-27101
Goto Forum:
  


Current Time: Wed Dec 07 02:42:13 CST 2016

Total time taken to generate the page: 0.11253 seconds