Primary Database Setting - Standby Database

Printable View

09-30-2002, 11:43 PM
ckwan

Hi All,
I have problem to startup the primary database for my standby database setup. Both Primary and Standby are the same host.

Primary - initmydb.ora
log_archive_start = true
log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
log_archive_dest_1="d:\oracle\oradata\mydb\archive\"
log_archive_dest_state_1=ENABLE
log_archive_dest_2="SERVICE=STBY MANDATORY REOPEN=30"
log_archive_dest_state_2=ENABLE

Standby - initstby.ora
log_archive_start = true
log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
standby_archive_dest="d:\oracle\oradata\stby\archive"
db_file_name_convert="d:\oracle\oradata\mydb","d:\oracle\oradata\stby"
log_file_name_convert="d:\oracle\oradata\mydb\archive","d:\oracle\oradata\stby\archive"
lock_name_space=STBY

I can managed to startup the secondary with nomount mode and startby database successfully but not the primary database.

I have following error message when I start primary DB :
SQL> startup pfile=d:\oracle\admin\mydb\pfile\initmydb.ora
LRM-00101: unknown parameter name 'SERVICE'
LRM-00101: unknown parameter name 'SERVICE'
LRM-00111: no closing quote for value '30"
log_ar'
ORA-01078: failure in processing system parameters

Thanks for any feedback given.
10-01-2002, 02:11 AM
pando

log_archive_dest_1 = "LOCATION=/archive1"
log_archive_dest_2 = "SERVICE=standby_db1"

I think you log_archive_dest_1 syntax is wrong
10-01-2002, 02:18 AM
ckwan

Thanks for the reply but I still has error

SQL> startup pfile=D:\oracle\admin\mydb\pfile\initmydb.ora
LRM-00111: no closing quote for value 'STBY"
log_'
ORA-01078: failure in processing system parameters

I had change as follow
log_archive_start = true
log_archive_max_processes = 10
log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
# log_archive_dest=d:\oracle\oradata\mydb\archive\
log_archive_dest_1="LOCATION=d:\oracle\oradata\mydb\archive\"
log_archive_dest_state_1=ENABLE
log_archive_dest_2="SERVICE=STBY"
log_archive_dest_state_2=ENABLE
10-01-2002, 03:12 AM
jmodic

Quote:

Originally posted by ckwan
log_archive_dest_2="SERVICE=STBY"

Try changing the above into:

log_archive_dest_2='SERVICE=STBY'

Use single quotes instead of double quotes.
10-01-2002, 03:17 AM
ckwan

After I changed the log_archive_dest_2 = 'SERVICE=STBY'

LRM-00111: no closing quote for value 'LOCATION=d'
LRM-00113: error when processing file 'd:\oracle\admin\mydb\pfile\initmydb.ora'
ORA-01078: failure in processing system parameters

I get this error then I also modify the log_archive_dest_1
to become log_archive_dest_1 = 'LOCATION=d:\oracle\oradata\mydb\archive\'

I get another error

LRM-00101: unknown parameter name 'SERVICE'
ORA-01078: failure in processing system parameters

it seems quite 'challenge' to setup the standby database.
10-01-2002, 03:31 AM
jmodic

Quote:

Originally posted by ckwan
I get this error then I also modify the log_archive_dest_1
to become log_archive_dest_1 = 'LOCATION=d:\oracle\oradata\mydb\archive\'

I belive that last backslash is the culprit of all your troubles! It shouldn't be there. I belive Oracle is interpreting it as an escape character, so the following quote character does not act as an enclosing quote. So Oracle is interpreting path for the LOCATION way down to the next quote chaqracter, which is before SERVICE keyword in log_archive_dest_2 parameter. So it is interpreting the word SERVICE as the next parameter, which of course is unknown and invalid as a parameter.

Remove that backslash and let us know if it has solved your problem.

Quote:

Originally posted by ckwan
it seems quite 'challenge' to setup the standby database

I've setup standby at least 10 times and never had any major problems ;).
10-01-2002, 03:35 AM
ckwan

Thanks for the prompt reply.

After I removed the black slash (\) I have following error

SQL> startup
ORA-00439: feature not enabled: Managed Standby
10-01-2002, 03:37 AM
ag_201074

guess your
log_archive_dest_1 = 'LOCATION=d:\oracle\oradata\mydb\archive\'

should
be
log_archive_dest_1 = 'LOCATION=d:\oracle\oradata\mydb\archive'

ie there shd be no "\" at the end of path ....
10-01-2002, 03:50 AM
jmodic

Quote:

Originally posted by ckwan
SQL> startup
ORA-00439: feature not enabled: Managed Standby

This is becoming a bit teasing :D. My guess is you are using Oracle Standard Edition. To use LOG_ARCHIVE_DEST_n parameters (in other words, to implement managed standby configuration) you need Enterprise Edition.

Can you provide details about the database release and type (Enterprise, Standard, Personal) you are using?
10-01-2002, 04:28 AM
ckwan

I checked my installer is an Enterprise Edition. Is there any other faster way to check the Edition I have currently ?
10-01-2002, 04:31 AM
ckwan

SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle8i Release 8.1.7.4.1 - Production
PL/SQL Release 8.1.7.4.0 - Production
CORE 8.1.7.2.1 Production
TNS for 32-bit Windows: Version 8.1.7.4.0 - Production
NLSRTL Version 3.4.1.0.0 - Production
10-01-2002, 04:33 AM
jovery

The v$version view will show which edition.

Regards
10-01-2002, 04:35 AM
jovery

Or you can look in v$option to make sure managed standby is TRUE

Regards
10-01-2002, 04:36 AM
ckwan

Sorry I can't any indicator for whether is Enterprise or not
10-01-2002, 04:40 AM
jovery

From the entries in your v$version view I would say your running standard verison.

Have you recently upgraded the software to EE? If so you will need to rerun the cataloge scripts to make use of the EE features on an instance.

Regards
10-01-2002, 04:41 AM
ckwan

After I selected all the rows from v$option, I found my Managed Standby value is FALSE.

But I checked from installer the database is the Enterprise Edition. Why ?
10-01-2002, 05:00 AM
ckwan

Recently I upgraded my Database from 8.1.7.0.0 to 8.1.7.4.1 due to some bugs in the previous version. I upgraded the database by following the release notes instruction. And in this upgrade I need to run the catalog and catproc as following
?/rdbms/admin/catalog.sql
?/rdbms/admin/catproc.sql

After run this my database version is already become 8.1.7.4.1

I had checked the documentation about the patch I applied,
as follow

Bug 1809786 Fixed: 8174
Recovery
Standby database may fail to open on same node as the primary (ORA-1102).

But this suppose already fix in my this release already.

Anyone have suggestion on this?
10-01-2002, 07:12 AM
anandkl

Query v$version, u will get which edition of oralce u r using.

regards
anandkl
10-01-2002, 08:14 AM
nagarjuna

ckwan,
nooooooo way, you can set up the standby database with this configuartion. ;) We can not use the same host for primary and standby database.

Others,
Read the 1st message of thread ;)
10-01-2002, 08:22 AM
jovery

Quote:

Originally posted by nagarjuna
ckwan,
nooooooo way, you can set up the standby database with this configuartion. ;) We can not use the same host for primary and standby database.

Others,
Read the 1st message of thread ;)

You can have a standby running on the same host but you need to make a few parameter and file changes

http://support.oracle.co.uk/metalink..._id=117399.996

Regards
10-01-2002, 08:44 AM
jmodic

Quote:

Originally posted by nagarjuna
Others,
Read the 1st message of thread ;)

Nagarjuna,

Read the following Standby Database Manual:
http://otn.oracle.com/docs/products/...a76995/toc.htm

And also read about the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in Reference manual.

You'll find out that having both primary and standby on the same hoset is totaly valid and doable. As a matter of fact, I have such a configuration right now on my laptop. Obviously not for disaster recovery purposes, though :D.
10-01-2002, 10:27 AM
nagarjuna

Quote:

Originally posted by jmodic

Quote:

Originally posted by nagarjuna
Others,
Read the 1st message of thread ;)

Nagarjuna,

Read the following Standby Database Manual:
http://otn.oracle.com/docs/products/...a76995/toc.htm

And also read about the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in Reference manual.

You'll find out that having both primary and standby on the same hoset is totaly valid and doable. As a matter of fact, I have such a configuration right now on my laptop. Obviously not for disaster recovery purposes, though :D.

oh.. Can you open both the primary and standby databases at the same time?? Dont you get "can not open the database in exclusive mode" kind of error?? I dont remember the exact error msg. But, we get such error msg when we try to open both the databases at the same.

And yep.. I know the concepts of standby database and db_file_convert and log_file_convert parameters.. :)
10-01-2002, 11:43 AM
jmodic

[QUOTE]Originally posted by nagarjuna

Quote:

oh.. Can you open both the primary and standby databases at the same time?? Dont you get "can not open the database in exclusive mode" kind of error?? I dont remember the exact error msg. But, we get such error msg when we try to open both the databases at the same.

No, I don't get any error mesage, I can open both databases (standby only in read-only mode, of course). Anyway, why would Oracle try to open any of the two databases in exclusive mode?
10-01-2002, 09:33 PM
ckwan

Anyway I will try to install Oracle 9i Enterprise Edition in my machine to try this feature again. I know there are some enhancement on the Standby - such as FAL_CLIENT and FAL_SERVER.

Alright, I will try it out and let ur all know the outcome.

Thanks a lot.
10-02-2002, 05:49 AM
nagarjuna

[QUOTE]Originally posted by jmodic

Quote:

Originally posted by nagarjuna

Quote:

oh.. Can you open both the primary and standby databases at the same time?? Dont you get "can not open the database in exclusive mode" kind of error?? I dont remember the exact error msg. But, we get such error msg when we try to open both the databases at the same.

No, I don't get any error mesage, I can open both databases (standby only in read-only mode, of course). Anyway, why would Oracle try to open any of the two databases in exclusive mode?

oh.. :o this is news for me. I should try.. :)