on 04-17-2007 1:27 PM
Dear support,
We are upgrading our 4.0B system hich is on NT 4.0 platform to 4.7. I have finished upgrading oracle 8.0.4.0 to 8.1.7.4 and now we are in a process of migrating OS from NT to win 2000. I am trying to do system copy from NT system to 2000 machine with same database and sap kernel level.But after creation of controlfile script i am getting below error when i try to give
(c) Copyright 2000 Oracle Corporation. All rights reserved.
SQL> connect /as sysdba
Connected to an idle instance.
SQL> startup nomount
ORA-16032: parameter LOG_ARCHIVE_DEST destination string cannot be translated
ORA-09291: sksachk: invalid device specified for archive destination
OSD-04018: Unable to access the specified directory or device.
O/S-Error: (OS 2) The system cannot find the file specified.
SQL> exit
Disconnected
Please let me know whether it is because of OS difference that database is not even getting to nomount stage.
waiting for early reply.
Best Regards,
AjitR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"<b>OSD-04018: Unable to access the specified directory or device.
O/S-Error: (OS 2) The system cannot find the file specified.</b>"
the actual db configuration is not able to find the archive destination...
-> how did you do the system copy?
-> did you follow sapnote(s)?
-> did you edit the control-files accordingly?
-> did you restart the oracle services?
GreetZ, AH
Yes i have done system copy twice for NT 4.0 DEV system before we went ahead with upgrade project. But this upgrade project includes migrating OS from NT 4.0 system which is now on Oracle 8.1.7.4 to WIN 2000 server where upgradation to 4.7 version is possible. On NT 4.0 it is not possible.My system copy methodology is correct but this time source system is on NT 4.0 and target system is on win 2000 server. So i wanted to know how this can be made possible if answer is yes?
If u have any more suggesion that we should directly upgrade our OS from NT 4.0 to WIn 2000 server without touching database then please tell me whether it is correct method or option to workout instead of my method which involves first move database to win 2000 machine and then go ahead with upgrade issue.
Because i am not confident enough of upgrading OS directly from NT 4.0 to WIn 2000 even though database version is copatible for 2000 OS.
-> how about the archive destination? is it there? accessable?
-> how about init<SID>.ora?
<u>another way/possible workaround:</u>
as you will have to go for oracle 9.2 anyway (even 10.2 is a choice) you could export the db using sapinst/r3setup under nt and copy the export to the win2k machine + doing the import (r3load method) using oracle 9.2...this is possible!
GreetZ, AH
If i do export import then it will be heterogeneous system copy method , and that would be my last option as same thing suggested by SAP people.But in sap standard document they recommend to upgrade OS at this point to 2000
INIT.ora for ur reference
@(#)initSID.ora 20.4.6.1 SAP 98/03/30
###########################################################
(c)Copyright SAP AG, Walldorf #
###########################################################
#INIT.SID Template for R/3 on Oracle 8.1.5 on NT
#Update this file according to note 180605
always_anti_join = hash
bitmap_merge_area_size = 33554432
compatible = 8.1.6
control_file_record_keep_time = 30
cursor_space_for_time = false
create_bitmap_area_size = 33554432
db_block_lru_latches = 2
db_block_size = 8192
db_file_multiblock_read_count = 8
db_files = 254
hash_area_size = 4194304
hash_join_enabled = true
hash_multiblock_io_count = 8
log_archive_start = true
log_buffer = 1048576
log_checkpoint_interval = 300000
log_checkpoint_timeout = 0
max_dump_file_size = 20000
open_cursors = 800
optimizer_mode = choose
parallel_broadcast_enabled = true
parallel_execution_message_size = 8192
parallel_max_servers = 4
processes = 100
row_locking = always
shared_pool_reserved_size = 10000000
sessions = 110
sort_area_retained_size = 0
sort_area_size = 2097152
star_transformation_enabled = true
timed_statistics = true
transaction_auditing = false
CONTROL-FILES
the controlfiles should be mirrored to every new
database mount point @SAPDATA_HOME@\sapdata<#>
#control_files = (@SAPDATA1@\cntrl\cntrlPRD.dbf, @SAPDATA2@\cntrl\cntrlPRD.dbf, @SAPDATA3@\cntrl\cntrlPRD.dbf)
DB-NAME
db_name = PRD
PATHS / DESTINATIONS / TRACES
F:\oracle\PRD\saptrace\background: trace files of the background
processes
F:\oracle\PRD\saptrace\usertrace: trace files of the user processes
log_archive_dest is a destination, not a path.
The archivefiles get the name
F:\oracle\PRD\saparch\PRDarch<thread#>_<log#>
background_dump_dest = F:\oracle\PRD\saptrace\background
user_dump_dest = F:\oracle\PRD\saptrace\usertrace
log_archive_dest = F:\oracle\PRD\saparch\PRDarch
#log_archive_format = %t_%s
shared_pool_size = 331517788
shared_pool_reserved_size = 33151778
db_block_buffers = 60702
control_files = ( E:\oracle\PRD\sapdata1\cntrl\cntrlPRD.dbf,E:\oracle\PRD\sapdata2\cntrl\cntrlPRD.dbf,E:\oracle\PRD\sapdata3\cntrl\cntrlPRD.dbf )
MAX_ROLLBACK_SEGMENTS = 400
rollback_segments = (PRS_0,PRS_1,PRS_2,PRS_3,PRS_4,PRS_5,PRS_6,PRS_7,PRS_8,PRS_9,PRS_10,PRS_11,PRS_12,PRS_13,PRS_14,PRS_15,PRS_16,PRS_17,PRS_18,PRS_19)
Freiends please help,
I have resolved previous issue but now after creation of controlfile new error found
as below
SQL> @c:\controlprd.sql
ORACLE instance started.
Total System Global Area 861194268 bytes
Fixed Size 75804 bytes
Variable Size 362790912 bytes
Database Buffers 497270784 bytes
Redo Buffers 1056768 bytes
Control file created.
SQL> recover database until cancel;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 12814179 generated at 04/16/2007 21:00:54 needed for thread 1
ORA-00289: suggestion : E:\ORACLE\PRD\SAPARCH\PRDARCH\ARC00025.001
ORA-00280: change 12814179 for thread 1 is in sequence #25
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
SQL> recover database using backup controlfile until cancel;
ORA-03114: not connected to ORACLE
As per log your Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
>>Check your db status,
SQL> recover database using backup controlfile until cancel;
ORA-03114: not connected to ORACLE
Cheers,
-Sunil
After going through your notes i dont think we have anything wrong with
methodology we are using as we have done system copy for this system and others many times but still this time source system is on NT 4.0 and target system is on win 200 server machine so, this problem might have occured.
Also please suggess is there any other option available to migrate OS to win 2000 instead doing system copy , as directly upgrading OS from NT to 2000 is how much safe for currently running system we are not so sure
about it? Even the database is on version 8.1.7.4 which is compatible for win 2000 server , still we dont know to take risk or not.Please let us know either solution or work around for this problem.
We have successfully created controlfile but now another error is coming after i issue recover command as below
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 12814181 generated at 04/17/2007 20:16:05 needed for thread 1
ORA-00289: suggestion : E:\ORACLE\PRD\SAPARCH\PRDARCH\ARC00001.001
ORA-00280: change 12814181 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'E:\ORACLE\PRD\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'
ORA-01112: media recovery not started
Please let us know how to go ahead at earliest.
Neither recovery is getting completed nor database is opening with resetlogs option.One more thing database of source system was in NOarchivelog mode so we cannot provide any REDO while it asks for recovery , we have to cancel it.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.