Академический Документы
Профессиональный Документы
Культура Документы
2. Copy the following folders and file from the source machine to target machine.
FOLDERS:xxxxxxxxxxxxxx, ssid
FILES: xxxxxxxxxxxxxx.ffd
3. next open .ffd file and change all SSID to Tsid .(ssid=source sid,tsid=target sid)
4. next change D:\oracle\TSID\SAPBACKUP (SSID TO TSID).
5. open the file INITSSID.SAP and change the file name to INITTSID.SAP in the
above path
6. then open the xxxxxxxxx folder and change SSID TO TSID path for all datafiles
which resides in folder (manually)
7. go to D:\ORACLE\ORA92\DATABASE\INITSID.SAP,open this file and change
BACK_DEV_TYPE : DISK (CHANGE FROM TAPE TO DISK)
8. shut down the database by using sapdba option
9.the services which are related to oracle and sap should b stopped.
1.oracleorahome92agent. 1.saposcol
2.oracleorahome92tnslistner 2. sapsid_nr
3.oracleservicesid
1.oracleorahome92agent. 1.saposcol
2.oracleorahome92tnslistner 2. sapsid_nr
3.oracleservicesid
17. when we generate the control file the database status is in mount state and we
should change to open state by using following command
sql>select status from v$instance;
it displays status as mounted.
sql>ALTER DATABASE OPEN;
18.when we use this command it prompts u that this command must go with one of
the following options
1.RESETLOGS
2.NORESETLOGS.
19.again run the above command with one of the above options
sql>ALTER DATABASE OPEN RESETLOGS;
20.then the database status will be in open state.
sql>SELECT STATUS FROM V$INSTANCE;
then database status will be shown as OPEN
21.if we get any warnings when we complete the restoration we have to execute the
following file
SAPDBA_ROLE.SQL
22.to execute the above file do the following process
a.copy that particular file from kernel directory (run folder) to d:/
drive
b.open it and give execute:owner:'sapsid' and change that sapsid to
u r targetsid.
c.run the above file as follows
d:/>sqlplus /no log @sapdba_role.sql tsid nt
d. here it will write the log file to the same directory where ur
sapdba_role.sql resides and it contains the log as permissions granted
23.If it is R/3 4.7 box(server) then we need to change the schema of target host to
source schema i.e.., SAP<SID>
mycomp-->advance--->environmentvariables--
>ORA_DB_SCHEMA--->EDIT--->SAP<SOURCESID>--->OK.
NOTE
But if it is ECC or net weaver then no need to change the schema coz the schema
will be same it will not change the slandered schema is “SAPSR3”