on 12-10-2007 8:05 PM
Hi forum,
in the CONTROL.SQL file there is the description of the source database, in the target system I need to change the <SID> name... is R3COPY executed into target system that change the name/path in CONTROL.SQL ?
I ask this because I've just receive a CONTROL.SQL for a remote (source) system and this file con contains source <SID> (database name and path) and not my new target <SID> name.
Regards.
Ganimede Dignan.
simply do a SEARCH and REPLACE from old SID to the new SID.
check the homogeneous system copy guide to know how to do this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hold on.. you told us that you have a copy of control.sql.
why do you need us to send ours?
check the following link for instructions:
Hi,
into documentation in section...
svrmgrl
SVRMGR> connect internal
SVRMGR> @/<path_to_file>/control.sql
I'm in a 9.2 Oracle Box so svrmgrl should be retired, so.. what are the right syntax to use sqlplus and run my custom control.sql ?
If I run...
bash-3.00$ sqlplus /nolog
SQL*Plus: Release 9.2.0.7.0 - Production on Tue Dec 11 20:22:56 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect / as sysdba
Connected to an idle instance.
SQL> exit
Disconnected
bash-3.00$
it should be OK.
Regards.
Ganimede Dignan.
Hi,
also in hom. system copy documentation at page 6-9 there are some commands to run with svrmgrl :
The database is now in NOARCHIVELOG mode. Change the mode to
ARCHIVELOG. Shut the database down and enter:
svrmgrl
SVRMGR> connect internal;
SVRMGR> startup mount;
SVRMGR> alter database srchivelog;
SVRMGR> alterdatabase open;
SVRMGR> exit
but on my system there isn't a svrmgrl binary command in $ORA_HOME\bin
bash-3.00# svrmgrl
bash: svrmgrl: command not found
bash-3.00#
How can I execute the same command in sqlplus ?
Regards.
bash-3.00$ sqlplus "/ as sysdba"
SQL*Plus: Release 9.2.0.7.0 - Production on Tue Dec 11 20:44:45 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to an idle instance.
SQL> connect internal
Enter password:
ERROR:
ORA-09275: CONNECT INTERNAL is not a valid DBA connection
Warning: You are no longer connected to ORACLE.
SQL>
Hello,
my first question would be
- do you have access to the oracle documentation?
- If so, have you ever read it?
or SAP notes about Oracle?
svrmgrl is an obsolete command, it has been replaced by sqlplus
"connect internal" is NOT used anymore ( also obsolete )
you have done:
bash-3.00$ sqlplus "/ as sysdba"
you do not need to issue any other command to connect as you are already connected ( with sysdba privileges):
Connected to an idle instance.
You must follow the OFFICIAL SAP documentation, where the correct steps are indicated.
Not try to follow blindly an obsolet document ( where you cannot recognize the differences )
>You must follow the OFFICIAL SAP documentation, where the correct steps are >indicated.
>Not try to follow blindly an obsolet document ( where you cannot recognize the >differences )
.. ehmmm, Official SAP documentattion about R/3 46C (also for 46D basis based system) write about svrmgrl and not sqlplus.
Bye.
Hi,
now I've an error... after restore of datafile, log, ecc. I run che script CONTROL.SQL with now sid name from sqlplus. I restart R3SETUP...
INFO 2007-12-12 09:37:37
Creating the Database User
SQL*Plus: Release 9.2.0.7.0 - Production on Wed Dec 12 09:37:37 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
old 6: if length('&&1') = 5 then
new 6: if length('SAP<TARGET_SID>') = 5 then
old 7: if substr(upper('&&1'),1,5) = 'SAPR3' then
new 7: if substr(upper('SAP<TARGET_SID>'),1,5) = 'SAPR3' then
old 10: if upper('&&2') = 'NT' then
new 10: if upper('UNIX') = 'NT' then
old 17: :sDomain := upper('&&3');
new 17: :sDomain := upper('<TARGET_SID>');
old 18: :sSapSid := upper('&&4');
new 18: :sSapSid := upper('x');
old 20: :sSapSid := upper('&&3');
new 20: :sSapSid := upper('<TARGET_SID>');
old 36: :sSchema := upper('&&1');
new 36: :sSchema := upper('SAP<TARGET_SID>');
old 37: if upper('&&2') = 'NT' then
new 37: if upper('UNIX') = 'NT' then
old 44: :sDomain := upper('&&3');
new 44: :sDomain := upper('<TARGET_SID>');
old 45: :sSapSid := upper('&&4');
new 45: :sSapSid := upper('x');
old 47: :sSapSid := upper('&&3');
new 47: :sSapSid := upper('<TARGET_SID>');
using following Parameters:
.
. Oracle Version: 9.2.0.7.0
. Parametervalue os_authent_prefix: OPS$
. Schema Id: <TARGET_SID>
. Database User (Schema): SAP<TARGET_SID>
. SAP R/3 Administrator: OPS$<TARGET_SID>ADM
.
unable to assign default tablespace to user: SAP<TARGET_SID>
begin
*
ERROR at line 1:
ORA-00959: tablespace 'PSAP<TARGET_SID>USR' does not exist
ORA-06512: at line 90
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.7.0 - Production
ERROR 2007-12-12 09:37:37 ORADBUSR_IND_ORA ExecuteCheck:0
Exit code from /oracle/<TARGET_SID>/920_64/bin/sqlplus: 191.
bash-3.00$ lsnrctl start
LSNRCTL for Solaris: Version 9.2.0.7.0 - Production on 12-DEC-2007 10:16:45
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Starting /oracle/NVQ/920_64/bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 9.2.0.7.0 - Production
System parameter file is /oracle/NVQ/920_64/network/admin/listener.ora
Log messages written to /oracle/NVQ/920_64/network/log/listener.log
Error listening on: (ADDRESS=(PROTOCOL=IPC)(KEY=NVQ.WORLD))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Solaris Error: 2: No such file or directory
Listener failed to start. See the error message(s) above...
>hold on.. you told us that you have a copy of control.sql.
>
>why do you need us to send ours?
>
>check the following link for instructions:
>
>http://www.basisconsultant.com/docs/handbooks/homcopyv1.pdf
This link is invalid... could you post me again a valid link, douc it's really nice.
Thank you for attention.
Regards.
Hello,
No. R3copy at the source system asks you the destination SID, and generates and adapts the control.sql file to this new system. It also creates the init<NEW_SID>.ora file, that you must copy to the target too.
At the target system, R3copy just process the control.sql file and generates the new DB controlfiles.
Best Regards,
JC Llanes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
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.