Home » Server Options » Data Guard » ORA-01154: database busy. Error in Creating Physical StandBy Database in the same Server (Oracle Release 10.2.0.1.0 / Windows 2003 Server Enterprise Edition SP2)
ORA-01154: database busy. Error in Creating Physical StandBy Database in the same Server [message #476060] Tue, 21 September 2010 03:27 Go to next message
artisteprasanna
Messages: 15
Registered: July 2010
Junior Member
Hi All,

I am trying to create the Physical StandBy Database in the same server. Till last 2 Final steps, everything went on well. In the final steps, when I try to open the StandBy Database, it throws the following Error:
*******************************************************
SQL...> alter database open;
alter database open
*
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now

*******************************************************
I tried creating the Physical Standby with the following Steps. Please look into that & tell me whether I have done any mistake.
Also tell me any step I have missed from the following list of steps:

Environment: Oracle Release 10.2.0.1.0 / Windows 2003 Server Enterprise Edition SP2
Primary DB = 'PrimDB'
StandBy DB to be created = 'StBy1DB'


In the same Server, location for
PrimDB datafiles = 'F:\oracle\product\10.2.0\oradata\PrimDB\Data\',
StandBy Datafiles = 'E:\StandBy_DB\Data\'

PrimDB Control Files = 'F:\oracle\product\10.2.0\oradata\PrimDB\Control\'
StandBy Control Files = 'E:\StandBy_DB\Control\'

PrimDB audit_file_dest = 'F:\oracle\product\10.2.0\oradata\PrimDB\Admin\adump\'
PrimDB background_dump_dest = 'F:\oracle\product\10.2.0\oradata\PrimDB\Admin\bdump\'
PrimDB core_dump_dest = 'F:\oracle\product\10.2.0\oradata\PrimDB\Admin\cdump\'
PrimDB user_dump_dest = 'F:\oracle\product\10.2.0\oradata\PrimDB\Admin\udump\'

StandBy audit_file_dest = 'E:\StandBy_DB\Admin\adump\'
StandBy background_dump_dest = 'E:\StandBy_DB\Admin\bdump\'
StandBy core_dump_dest = 'E:\StandBy_DB\Admin\cdump\'
StandBy user_dump_dest = 'E:\StandBy_DB\Admin\udump\'


PrimDB Online Redo Log = 'F:\oracle\product\10.2.0\oradata\PrimDB\REDO\'
StandBy Online Redo Log = 'E:\StandBy_DB\Redo\'

PrimDB Archive Log = 'F:\oracle\product\10.2.0\oradata\PrimDB\Archive\'
StandBy Archive Log = 'E:\StandBy_DB\Archive\'



Step 1 Create the Oracle Service for StandBy DB "StBy1DB' and Create the Standy DB Password file.

ORADIM -NEW -sid StBy1DB -intpwd passwd -startmode manual

Step 2 Shut down the primary database.

SQL> SHUTDOWN IMMEDIATE;

Step 3 Copy the datafiles to 'E:\StandBy_DB\Data\'. (including Temp01.dbf is it Right?)

Step 4 Restart the primary database.

Restart the primary database:

SQL> STARTUP;

Step 5 Create a Control File for the Standby Database (Should this command be given in Mount Status or Open Status?)

From Primary database,

SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'E:\StandBy_DB\Control\StByControl01.ctl';

Step 6 Prepare the Initialization Parameter File to be Copied to the Standby Database

SQL> CREATE PFILE='E:\StandBy_DB\PFile\initStBy1DB.ora' FROM SPFILE;


Step 7 Set Initialization Parameters on a Physical Standby Database


db_cache_size = 444596224

java_pool_size = 4194304

large_pool_size = 4194304

shared_pool_size = 150994944

streams_pool_size = 0

*.audit_file_dest = 'E:\StandBy_DB\Admin\adump\'

*.background_dump_dest = 'E:\StandBy_DB\Admin\bdump\'

*.core_dump_dest = 'E:\StandBy_DB\Admin\cdump\'

*.user_dump_dest = 'E:\StandBy_DB\Admin\udump\'
*.compatible = '10.2.0.1.0'
*.control_files = 'E:\StandBy_DB\Control\StByControl01.ctl'

*.db_block_size = 8192

*.db_name = 'PrimDB'

*.sga_target = 612368384

*.LOG_ARCHIVE_START = TRUE

*.standby_file_management = Auto

*.remote_archive_enable = True



############### Want to know the difference between

############### StandBy_ARCHIVE_DEST and log_ARCHIVE_DEST_1

############### StandBy_ARCHIVE_DEST - is the destination at StandBy Server. Am I Right?

############### log_ARCHIVE_DEST_1 - What is purpose of this destination?

*.StandBy_ARCHIVE_DEST = 'E:\StandBy_DB\ Archive\'

*.log_ARCHIVE_DEST_1 = 'LOCATION=E:\StandBy_DB\Archive\'


*.log_archive_format = Stby1Archive_%d_%t_%s_%r.arc


# Convert file names to allow for different directory structure.

*.db_file_name_convert = ('F:\oracle\product\10.2.0\oradata\PrimDB\Data', 'E:\StandBy_DB\Data\')

*.log_file_name_convert = ('F:\oracle\product\10.2.0\oradata\PrimDB\REDO', 'E:\StandBy_DB\Redo\')

*.db_unique_name = 'StndBy1'

*.instance_name = 'StndBy1'

*.FAL_Server = PrimDB

*.FAL_Client = StndBy1

# The following parameter is required only
# if the primary and standby databases
# are located on the same system.

*.lock_name_space = 'StndBy1'





Step 8 Configure Listener TCP with port 1521 for the Primary and Standby Databases, then

% lsnrctl stop
% lsnrctl start

Step 9 Enable Dead Connection Detection on the Standby System

SQLNET.EXPIRE_TIME=2

Step 10 Create Oracle Net Service Names for primary and standby databases

Step 11 Create a Server Parameter File for the Standby Database

SQL> CREATE SPFILE FROM PFILE='E:\StandBy_DB\PFile\initStBy1DB.ora';

Step 12 Start the Physical Standby Database

SQL> STARTUP NOMOUNT;
SQL> ALTER DATABASE MOUNT STANDBY DATABASE;

Step 13 Initiate Log Apply Services

On the standby database, start log apply services as shown:

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;


Now When I type the following command, it throws an error:


SQL...> alter database open;
alter database open
*
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now


Can anyone please help me in this issue?
Re: ORA-01154: database busy. Error in Creating Physical StandBy Database in the same Server [message #476070 is a reply to message #476060] Tue, 21 September 2010 04:01 Go to previous messageGo to next message
John Watson
Messages: 4515
Registered: January 2010
Location: Global Village
Senior Member
Are you trying to open your physical standby while it is recovering? You can't do that with 10g, only with 11g and the Real Time Query option.
Re: ORA-01154: database busy. Error in Creating Physical StandBy Database in the same Server [message #476076 is a reply to message #476070] Tue, 21 September 2010 04:29 Go to previous message
artisteprasanna
Messages: 15
Registered: July 2010
Junior Member
Thanks a lot, John, for your immediate response.

After I gave the command as stated in STEP 13, it said "Database Altered". When the error occurred, also I tried waiting for a long time.

1) Can you please tell me approx. what is the duration for the process to get completed?

2) How do I know whether recovery is completed or not.

3) Also I tried applying "Alter System Archive Log Current from the Primary database, nothing got reflected in StandBy. Should I have to create Any StandBy Log Groups/Members?

4) Should the Database protection mode be in "Maximum Availability"?

Thanks a lot.

Previous Topic: v$view to lookup last apply log in automatic recover standby database
Next Topic: FAL[client]: Error fetching gap sequence, no FAL server specified
Goto Forum:
  


Current Time: Sat Aug 30 07:55:57 CDT 2014

Total time taken to generate the page: 0.07838 seconds