Unable to fetch data in standby server...plz help

[prasad_njoy]

Hi...actually we dont know each other ....but i need your help.
I have successfully created a standby database using RMAN method in oracle10g.But i am not able to see the data which i have added on the primary server.I didnt get any error while creating a standby database.when i fire select database_role,switchover_status
2 from v$database; on both primary and standby server i get the correct Output as expected.But still when ever i insert a new record on primary server it doesnt get reflect on standby.Please help....Plzzzzzzzzzzzzzzzz

[davey23uk]

have the logs been shipped over the standby?

[prasad_njoy]

Thanks for your reply....
First i configured the listener.ora and tnsnames.ora files...
The files which i replaced over the standby server are...
1)init.ora
2)PWDorcl
3)redolog files
4)*.dbf

Then transfered the backupfiles from primary server to standby...
and follwed the procedure using the commands...and their was no error during the process...please tell me were i went wrong.

[PAVB]

Thank you for your answer but this is not what Dave asked you.

He's asking if you are shipping logs over the standby; how do you think standby database is going to be aware of changes made on primary database?

[prasad_njoy]

Can you please explain what exactly you mean by saying log files....and how to ship them over to standby,i am new to this technolgy...plz help

[davey23uk]

huh?

what guide did you follow to set up the standby then - have you asked your dba to help you out

do you even know what the log files are?

[prasad_njoy]

I followed the follwing procedure for creating satndby database.....the process runs successfully but i am not able to see changes on the standby server which i make on primary srever...Help


1. Setup the same Windows user accounts (Oracle software owner) and groups (dba) on the standby
server.
2. Recreate the same Oracle directory structure on the standby server as on the primary server.
3. Install Oracle software on the standby server preferably in the same location as on the primary
server.
4. Copy the init.ora file for the production database on the production server to the standby server.
5. Copy the password file %ORACLE_HOME%\dbs\orapw<$ORACLE_SID> from the production
server to the standby server. You may have to create a new password file with the orapwd utility.
6. Copy the spfile from the production server to the standby server if it is used.
7. Create an Oracle service for the standby database on the standby server with command (startmode
is manual):
oradim -new -sid dbvisitp -intpwd MYSECRETPASSWORD -startmode M
Where dbvisitp is the name of the database
8. Create a directory on the primary and standby server where the full backup of the database can be
kept. In this example C:\oracle\orabase\backupfile.
On the standby server:
9. Listener must be running on the standby server and you must be able to connect from primary
server to the standby database (the SQL*Net port must be open on any firewall between the two
servers).
10. Start the standby database in nomount mode.
$ sqlplus "/ as sysdba"
SQL> startup nomount
On the primary server:
11. Set the Oracle environment to the production database and start Rman:
$ rman
connect target /
run{
change archivelog all crosscheck;
allocate channel ch1 type disk;
backup incremental level 0 database format
'C:\oracle\orabase\backupfile\bk_inc0_%s_%p' setsize=8250000 include current
controlfile for standby ;
sql "alter system archive log current";
backup archivelog all format 'C:\oracle\orabase\backupfile\al_%s_%p';
release channel ch1;
}
Oracle is a registered trademark of Oracle Corporation
Copyright 2000-2007 Avisit Solutions Limited
www.dbvisit.com
12. Copy files from C:\oracle\orabase\backupfile\ to same location on standby server.
13. Create an alias entry for the standby database in the tnsnames.ora file on the production server. In
this example the alias is called standbydb.
14. Start Rman and create the standby database. The password for sys must be the password from the
password file.
$ rman
connect auxiliary sys/password@standbydb
connect target /
run {
allocate auxiliary channel ch1 type disk;
duplicate target database for standby dorecover nofilenamecheck;
release channel ch1;
}
15. Standby database is now complete. Rman has started the standby database in mount standby
mode which is correct for Dbvisit to continue. For reference the commands to start a standby
database are:
SQL> startup nomount
SQL> alter database mount standby database;
NOTE:
If the following message is received from Rman:
RMAN> connect auxiliary sys/password@standbydb
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04006: error from auxiliary database: ORA-12528: TNS:listener: all
appropriate instances are blocking new connections
Then the following should be added (in red) to the listener.ora on the standby server:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = dbvisitp)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
)
)
Where dbvisitp is the name of your database
Creating a standby database (traditional method) – for Microsoft Windows
The process involves making a full backup of your production database on the primary server. This can
be either a hot or a cold backup. If a hot backup is used, then the archive log files created during the
backup will also need to be copied to the standby database.
Preliminary steps:
1. Setup the same Windows user accounts (Oracle software owner) and groups (dba) on the
standby server.
2. Recreate the same Oracle directory structure on the standby server as on the primary server.
3. Install Oracle software on the standby server preferably in the same location as on the primary
server.
Oracle is a registered trademark of Oracle Corporation
Copyright 2000-2007 Avisit Solutions Limited
www.dbvisit.com
4. Copy the init.ora file for the production database on the production server to the standby
server.
5. Copy the password file %ORACLE_HOME%\dbs\orapw<$ORACLE_SID> from the production
server to the standby server. You may have to create a new password file with the orapwd
utility.
6. Copy the spfile from the production server to the standby server if it is used.
7. Create an Oracle service for the standby database on the standby server with command
(startmode is manual):
oradim -new -sid dbvisitp -intpwd MYSECRETPASSWORD -startmode M
Where dbvisitp is the name of the database
On the primary server:
8. Make a standby controlfile on the production database using the following command:
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS
'C:\oracle\orabase\admin\dbvisitp\create\STANDBY_DBVISIT_control01.ctl' REUSE;
Where dbvisitp is the name of the database
9. Copy this standby controlfile to a temporary location on the standby server.
10. Make a cold or a hot backup of the database to either disk or tape.
11. Restore the full production database backup (including any new archive logs) to the standby
server.
On the standby server:
12. Replace the existing controlfile(s) (if any) with the new standby controlfile from the temporary
location. Make sure the names of the controlfile(s) stay the same.
Example: if the existing controlfiles were named control01.ctl and control02.ctl, replace the
existing controlfiles with the new standby controlfile (created in step 8 above) and make sure
that new standby controlfiles are named control01.ctl and control02.ctl.
13. Set the correct Oracle environment.
14. Start sqlplus:
sqlplus /nolog
SQL> connect / as sysdba ;
SQL> startup nomount
SQL> alter database mount standby database ;
SQL> recover standby database ;
Specify log: {=suggested | filename | AUTO | CANCEL}
15. Apply archives until there are no more archives to be applied.
16. Standby database is now complete. The standby database is in mount standby mode which is
correct for Dbvisit to continue. For reference the commands to start a standby database are:
SQL> startup nomount
SQL> alter database mount standby database;

[davey23uk]

have you configured the logs to be shipped?

[prasad_njoy]

How to Configure the log files and ship them over stanby......
Please tell the procedure,be descriptive.
Thanks in advance !!

[vnktummala]

Prasad -

Would you mind to read the documentation?

http://download.oracle.com/docs/cd/B...t.htm#i1148216

Thanks,