Deadlock error on logical standby

Hi All,
I am get an issue where every thing is working fine on Db server but when it is getting replicated to Logical standby i am getting a deadlock error. Please find error logs below
Fri May 20 21:00:56 2011
ORA-00060: Deadlock detected. More info in file /u01/logicalstdby_home/product/admin/XXXXX/bdump/xxlog_p004_15175.trc.
Fri May 20 21:00:56 2011
8
Errors in file /u01/logicalstdby_home/product/admin/XXXXX/bdump/xxlog_lsp0_2207.trc:
ORA-12801: error signaled in parallel query server P004
ORA-00060: deadlock detected while waiting for resource
9
ORA-12801: error signaled in parallel query server P004
ORA-00060: deadlock detected while waiting for resource
LOGSTDBY Analyzer process P003 pid=42 OS id=15173 stopped
Please can anyone help in investigation.
Thanks and Regrads,
Amol

Hi ,
I have the logs from deadlock file.
There are two queries in this dump. Does this mean that the two queries in the logs (which are actually same) are runing in parellel. Because this actually ran fine on the primary database.
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-01350024-00098ad3 44 804 X 46 797 S
TX-012f0006-0008ac28 46 797 X 60 874 S
TX-01340000-000a175c 60 874 X 44 804 S
session 804: DID 0001-002C-0003E40C     session 797: DID 0001-002E-00002364
session 797: DID 0001-002E-00002364     session 874: DID 0001-003C-0000019C
session 874: DID 0001-003C-0000019C     session 804: DID 0001-002C-0003E40C
Rows waited on:
Session 797: obj - rowid = 00000000 - D/////AAaAAHqeAAAA
(dictionary objn - 0, file - 26, block - 2008960, slot - 0)
Session 874: obj - rowid = 00089976 - AAC5PjAAFAAAmj+AAA
(dictionary objn - 563574, file - 5, block - 157950, slot - 0)
Session 804: obj - rowid = 00089976 - AAC5PjAAFAAAmi3AAA
(dictionary objn - 563574, file - 5, block - 157879, slot - 0)
Information on the OTHER waiting sessions:
Session 797:
pid=46 serial=418 audsid=0 user: 0/SYS
O/S info: user: oracle, term: UNKNOWN, ospid: 15180, machine: db5p
program: oracle@db5p (P006)
Current SQL Statement:
update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
Session 874:
pid=60 serial=20958 audsid=0 user: 0/SYS
O/S info: user: oracle, term: UNKNOWN, ospid: 15182, machine: db5p
program: oracle@db5p (P007)
Current SQL Statement:
update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
End of information on OTHER waiting sessions.
Current SQL statement for this session:
update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
===================================================
PROCESS STATE
Process global information:
process: 0x29c53bcc8, call: 0x29567f358, xact: 0x299db2d90, curses: 0x29c811dd8, usrses: 0x29c811dd8
SO: 0x29c53bcc8, type: 2, owner: (nil), flag: INIT/-/-/0x00
(process) Oracle pid=44, calls cur/top: 0x29567f358/0x29567eb18, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 117
last post received-location: kcbzww
last process to post me: 29c53fc08 42 0
last post sent: 0 0 117
last post sent-location: kcbzww
last process posted by me: 29c53c4b0 188 0
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 0x29f601e88
O/S info: user: oracle, term: UNKNOWN, ospid: 15175
OSD pid info: Unix process pid: 15175, image: oracle@db5p (P004)
Dump of memory from 0x000000029C500F08 to 0x000000029C501110
29C500F00 00000002 00000000 [........]
29C500F10 9C811DD8 00000002 00000004 0003129B [................]
29C500F20 8F34B7A0 00000002 0000001E 0003115B [..4.........[...]
29C500F30 9CA03A98 00000002 0000000B 000313A7 [.:..............]
29C500F40 9EBD0510 00000002 0000003D 0003115B [........=...[...]
29C500F50 9C803260 00000002 00000004 0003129B [`2..............]
29C500F60 75E66848 00000001 0000001E 0003115B [Hh.u........[...]
29C500F70 99507DB0 00000002 00000007 000313A7 [.}P.............]
29C500F80 99507F70 00000002 00000007 000313A7 [p.P.............]
29C500F90 995083D0 00000002 00000007 000313A7 [..P.............]
29C500FA0 99508CA8 00000002 00000007 000313A7 [..P.............]
29C500FB0 995093C0 00000002 00000007 000313A7 [..P.............]
29C500FC0 99509AC0 00000002 00000007 000313A7 [..P.............]
29C500FD0 9950AC58 00000002 00000007 000313A7 [X.P.............]
29C500FE0 9950B290 00000002 00000007 000313A7 [..P.............]
29C500FF0 9950D6A0 00000002 00000007 000313A7 [..P.............]
29C501000 994FDAB0 00000002 00000007 000313A7 [..O.............]
29C501010 99510640 00000002 00000007 000313A7 [@.Q.............]
29C501020 99510B80 00000002 00000007 000313A7 [..Q.............]
29C501030 99510FE0 00000002 00000007 000313A7 [..Q.............]
29C501040 99511298 00000002 00000007 000313A7 [..Q.............]
29C501050 99511998 00000002 00000007 000313A7 [..Q.............]
29C501060 99511A78 00000002 00000007 000313A7 [x.Q.............]
29C501070 99511B58 00000002 00000007 000313A7 [X.Q.............]
29C501080 99512350 00000002 00000007 000313A7 [P#Q.............]
29C501090 99513248 00000002 00000007 000313A7 [H2Q.............]
29C5010A0 99513408 00000002 00000007 000313A7 [.4Q.............]
29C5010B0 99513788 00000002 00000007 000313A7 [.7Q.............]
29C5010C0 9CA04DE8 00000002 0000000B 000313A7 [.M..............]
29C5010D0 995144C0 00000002 00000007 000313A7 [.DQ.............]
29C5010E0 99515038 00000002 00000007 000313A7 [8PQ.............]
29C5010F0 995152D8 00000002 00000007 000313A7 [.RQ.............]
29C501100 995159F0 00000002 00000007 000313A7 [.YQ.............]
Thanks,
Amol

Similar Messages

Database Guard enabled error in Logical standby database

Hi All,
In my logical standby db i have a schema REP which is not present in Primary database, but even then i am getting ora-16224 Database Guard enabled error when ever i try DDL and DML operation on REP schema objects in Logical standby db.
even when i compile sys object i am getting the same error. when i set database data guard status to NONE, i don't get error, but my requirement is to keep database data guard status in STANDBY
My database version is 11.2.0.3.0.
Please help in resolving this error.
Thanks,
Mukesh

>In my logical standby db i have a schema REP which is not present in Primary database,
not possible

Error from Logical Standby

Dear All,
I have configured Logical Standby Database 10gR2, on Windows 2003 Server.
Logs are shipped and applied on the standby, without any issue.
I can log on logical database using sys account, but if i use any other user's account i get this error message:
SQL> connect user/pass
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-06550: line 11, column 52:
PL/SQL: ORA-16224: Database Guard is enabled
ORA-01017: invalid username/password; logon denied
ORA-06550: line 11, column 4:
PL/SQL: SQL Statement ignored
ORA-06550: line 17, column 28:
PL/SQL: ORA-16224: Database Guard is enabled
ORA-01017: invalid username/password; logon denied
ORA-06550: line 14, column 8:
PL/SQL: SQL Statement ignored
ORA-06550: line 20, column 12:
PLS-00513: PL/SQL function called from SQL must return value of legal SQL type
ORA-06550: line 12, column 4:
PL/SQL: Statement ignored
ORA-01017: invalid username/password; logon denied
I have copied the password file from live to standby.
Kindly help

Hi,
Did you sure connecting to standby database correct user and password ?
Did you getting following error on connection?
ERROR:
ORA-00604: error occurred at recursive SQL level 1
ORA-06550: line 11, column 52:
PL/SQL: ORA-16224: Database Guard is enabled
ORA-01017: invalid username/password; logon denied
ORA-06550: line 11, column 4:
PL/SQL: SQL Statement ignored
ORA-06550: line 17, column 28:
PL/SQL: ORA-16224: Database Guard is enabled
ORA-01017: invalid username/password; logon denied
ORA-06550: line 14, column 8:
PL/SQL: SQL Statement ignored
ORA-06550: line 20, column 12:
PLS-00513: PL/SQL function called from SQL must return value of legal SQL type
ORA-06550: line 12, column 4:
PL/SQL: Statement ignored
ORA-01017: invalid username/password; logon denied
Paste here your whole script.
Additionally please check: http://docs.oracle.com/cd/E11882_01/server.112/e25608/manage_ls.htm#SBYDB4811
10.2 Controlling User Access to Tables in a Logical Standby Database
Regards
Mahir M. Quluzade

Error when logical standby database

Hii all,
First time i am creating logical standby database on oracle 10gR2 by oracle doc.
but When i try to create logical standby database it give error
DG 2011-07-11-09:44:24 0 2 755997031 Operation CTL_GET_STATUS cancelled during phase 2, error = ORA-16797
DG 2011-07-11-09:44:24 0 2 755997031 Operation CTL_GET_STATUS cancelled during phase 2, error = ORA-16797
DG 2011-07-11-09:45:24 0 2 0 RSM0: HEALTH CHECK ERROR: ORA-16797: database is not using a server parameter file.
when i try to create spfile from pfile it give error.
ORA-01078 failure in processing initialization parameters.
LRM-00123 invalid character number found in the input file.
Please help
Vaibhav Dixit.

Vaibhav Dixit wrote:
stan.__db_cache_size=432013312
stan.__java_pool_size=4194304
stan.__large_pool_size=8388608
stan.__shared_pool_size=163577856
stan.__streams_pool_size=0
*.audit_file_dest='D:\oracle\product\10.2.0/admin/stan/adump'
*.background_dump_dest='D:\oracle\product\10.2.0/admin/stan/bdump'
*.compatible='10.2.0.1.0'
*.control_files='D:\oracle\product\10.2.0/oradata/stan/stan05.ctl'
*.core_dump_dest='D:\oracle\product\10.2.0/admin/stan/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='stan'
*.DB_UNIQUE_NAME='stan'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(prim,stan)'
*.DB_FILE_NAME_CONVERT='D:\oracle\product\10.2.0\oradata\prim\','D:\oracle\product\10.2.0\oradata\stan\'
*.LOG_FILE_NAME_CONVERT= ’D:\oracle\product\10.2.0\oradata\prim\’,’D:\oracle\product\10.2.0\oradata\stan\’,'D:\oracle\product\10.2.0\flash_recovery_area\prim\ONLINELOG','D:\oracle\product\10.2.0\flash_recovery_area\stan\ONLINELOG'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_DEST_1= 'LOCATION=D:\oracle\product\10.2.0\flash_recovery_area\stan\ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stan'
*.LOG_ARCHIVE_DEST_2= 'SERVICE=prim LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=prim'
*.LOG_ARCHIVE_DEST_3= 'LOCATION=D:\oracle\product\10.2.0\flash_recovery_area\STAN2\ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=stan'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_3='ENABLE'
*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
*.LOG_ARCHIVE_MAX_PROCESSES=30
*.STANDBY_FILE_MANAGEMENT='AUTO'
*.FAL_SERVER='prim'
*.FAL_CLIENT='stan'
*.db_recovery_file_dest_size=9390363648
*.dispatchers='(protocol=TCP)'
*.job_queue_processes=10
*.nls_territory='INDIA'
*.open_cursors=300
*.pga_aggregate_target=202375168
*.processes=150
*.sga_target=609222656
*.shared_servers=1
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='D:\oracle\product\10.2.0/admin/stan/udump'
*.undo_retention=3600
*.dg_broker_start='TRUE'from
'D:\oracle\product\10.2.0/admin/stan/udump'
please change or replace the forward slash with backward slash in all file locations
to
eg:- 'D:\oracle\product\10.2.0\admin\stan\udump'
and create a spfile from pfile.

Archive log shipping error in Logical standby database

Hi,
We have Primay and logical database configuration both in RAC in Production. both database are in 10.2.0.4.
Everyday we having issue of some archivelog not transfered to logical server around 2AM. I am having good exposure in Logical/Log minor/Goldgendate and can say fal server/client server configuration is correct.
Can you guys please give some input of what can cause this.
Yes we take RMAN backup of both database around 1:30 using control file instead of recovery catalog and I doubt this put lock on control file and cause this issue.
I would be glad of you could help me out in this.
Thanks a lot!
Pradeep
Below is the configuration of archive/fal on both database.
PIP1REP2 is logical database(instance 2) where apply process is running/configured.
Primary server configuration on (PIP11) (same are on other instances).
SQL> sho parameter fal
NAME TYPE VALUE
fal_client string PIP1REP2
fal_server string PIP11
SQL> sho parameter archive
NAME TYPE VALUE
log_archive_dest_1 string LOCATION=+ARCH01
log_archive_dest_2 string SERVICE=pip1rep2 lgwr async
log_archive_dest_state_1 string enable
log_archive_dest_state_2 string ENABLE
llog_archive_local_first boolean TRUE
log_archive_max_processes integer 10
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
Logical server configuration
SQL> sho parameter fal
NAME TYPE VALUE
fal_client string PIP1REP
fal_server string pip11, pip12, pip13, pip14, pi
p15
SQL> sho parameter archive
NAME TYPE VALUE
alog_archive_dest_1 string LOCATION=+ARCH01/PIP1REP valid
for=(onlinelogfiles, all_rol
es) db_unique_name=pip1rep
log_archive_dest_2 string LOCATION=+ARCH01/PIP1REP/ARCH_
DEST2_STANDBY_LOGS VALID_FOR=(
STANDBY_LOGFILES,STANDBY_ROLE)
db_unique_name=pip1rep
log_archive_dest_state_1 string enable
log_archive_dest_state_2 string enable
log_archive_local_first boolean TRUE
log_archive_max_processes integer 20
log_archive_min_succeed_dest integer 1
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string +ARCH01

Do you think creating recovery catalog will resolve it?
Yes, I do. (But I do not know for sure)
If it helps when I got to this part I decided to backup either the Primary or the Standby, but not both.
I decided Primary only and documented how to recreate my standby without downtime.
I hope this helps.
regards.

Physical vs Logical standby database

In the Oracle HA guide, it is mentioned that we must take Logical backup "in addition" to Physical backup (not instead of Physical Backup)
If I run have two systems i.e a Primary System and a Logical standby database system , is it not sufficient protection ? If the primary fails, can I not recover the primary system using the nightly backup I take from the Logical Standby Database.
If it is not sufficient protection, what exactly I will lose ?
Assume I take the nightly complete hot backup backup from the Logical Standby Database instead of the Primary System to save CPU cycles of the primary system.
In other words, it is said that "physical standby database provides zero data loss without any allowance for data divergence" -- What exactly is meant here ?

Thanks Werner for the reply.
1. If there is a human error (dropping a table by mistake), it will be applied to the standby database irrespective of whether it is physical standby or Logical standby. I am unable to see any advantage with Logical standby database in this case. Am I missing something here ?
Or are there any other type of user errors where Logical standby provides an advantage ? Can you please name some ?
2. If I backup from the logical database and if I am willing to "restore" (instead of recover) the primary from this backup in case of a primary failure, is it not the same effort ?
3. Can't we set up a Logical Standby with Maximum Protection Mode ?
I am aware physical standby offers a better performance and it has no data type restrictions. I do not care about these two. Also, I am aware of the extra features provided by Logical database.
Overall, I am trying to see whether physical standby database has any "feature" which I will miss with Logical standby database. I tried my best with Oracle documentation, but I could not get a clear answer.
Any help is appreciated.

Error while Creating a Logical Standby Database

Dears
I setup physical standby db. Now trying to convert it to logical standby db by following this link:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm#i92346
When i issue this statement:
ALTER DATABASE RECOVER TO LOGICAL STANDBY orcl2;
I am getting following error:
ORA-00905: missing keyword.
I do not find anything in ALERT.LOG file. The syntax seems to be correct as i carefully copied from the document itself.
Please reply.

Any ideas?

Logical Standby - Log Apply Error

Hi All
I have configured a 10.2.0.4 logical standby database (single instance) for RAC primary by LOG APPLY process stopped with this error:
ORA-01422: exact fetch returns more than requested number of rows.
Now I did run this command before creating logical standby: EXECUTE DBMS_LOGSTDBY.BUILD;
And I know that there are 80 tables which cannot be uniquely identified, which is fine by business.
Could you someone please tell how can I deal with this problem.
Regards
Amit

I have configured a 10.2.0.4 logical standby database (single instance) for RAC primary by LOG APPLY process stopped with this error:
ORA-01422: exact fetch returns more than requested number of rows.
Now I did run this command before creating logical standby: EXECUTE DBMS_LOGSTDBY.BUILD;
And I know that there are 80 tables which cannot be uniquely identified, which is fine by business.
Could you someone please tell how can I deal with this problem. It looks like a Bug too, check this below note
*Bug 5889516 - Intermittently ORA-1422 logical standby errors [ID 5889516.8]*

Logical standby error with export dump

oracal 10g have a setup logical standby and when i am running export dump from logical i got this error.
EXP-00008: ORACLE error 16224 encountered
ORA-16224: Database Guard is enabled
EXP-00000: Export terminated unsuccessfully
can someone help me out how can it posibal to take export dump and datapump from logical standby.
thanks

16224, 00000, "Database Guard is enabled"
// *Cause: Operation could not be performed because database guard is enabled
// *Action: Verify operation is correct and disable database guard

Creating a new schema in a Logical Standby Database

Hi All,
I am experimenting with logical standby databases for the purpose of reporting, and have not been able to create a new schema in the logical standby database - one of the key features of logical standbys.
I have setup primary and logical standby databases, and they seem to be running just fine - changes are moved from the primary to the standby and queries on the standby seem to run ok.
However, If I try to create a new schema on the logical standby, that does not exist on the primary, I get "ORA-01031: insufficient privileges" errors when I try to create new objects.
Show below are the steps I have taken to create the new schema on the logical standby. Any help would be greatly appreciated.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_new
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user new
2 identified by new
3 default tablespace ts_new
4 temporary tablespace temp
5 quota unlimited on ts_new
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to new
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to new
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to new
SYS@UATDR> select * from dba_sys_privs where grantee='NEW'
2 /
GRANTEE PRIVILEGE ADM
NEW CREATE ANY TABLE NO
NEW CREATE TABLE NO
NEW UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect new/new
Connected.
NEW@UATDR>
NEW@UATDR> -- prove ability to create tables
NEW@UATDR> create table new
2 (col1 number not null)
3 tablespace ts_new
4 /
create table new
ERROR at line 1:
ORA-01031: insufficient privileges
NEW@UATDR>
NEW@UATDR>

HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>

Logical standby and Primary keys

Hi All,
Why primary keys are essential for creating logical standby database? I have created a logical standby database on testing basis without having primary keys on most of the tables and it's working fine. I have not event put my main DB in force logging mode.

I have not event put my main DB in force logging mode. This is because, redo log files or standby redo logfiles transforms into set of sql statements to update logical standby.
Have you done any DML operations with nologging options and do you notice any errors in the alert.log? I just curious to know.
But I wanted to know that, while system tablespace in hot backup mode,In the absence of both a primary key and a nonnull unique constraint/index, all columns of bounded size are logged as part of the UPDATE statement to identify the modified row. In other words, all columns except those with the following types are logged: LONG, LOB, LONG RAW, object type, and collections.
Jaffar

Best practice on using Flashback and Logical Standby

Hello,
I'm testing a fail-back scenario where I first need to activate a logical standby, then do some dummy transactions before I flashback this db and resme the redo apply. Here is what the steps look like:
1)     Ensure logical standby is in-sync with primary
2)     Enable flashback on standby
3)     Create a flashback guaranteed restore point
4)     Defer log shipping from primary
5)     Activate the logical standby so it’s fully open to read-write
6)     Dummy activities against the standby (which is now fully open)
7)     Flashback the database to the guaranteed checkpoint
8)     Resume log shipping on primary
9)     Resume redo apply on secondary
In the end, i can see the log shipping is happening but the logical standby does not apply any of these..and there is no error in the alert log on Standby side. But the following query could explains why the standby is idle:
SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
TYPE HIGH_SCN STATUS
COORDINATOR ORA-16240: Waiting for log file (thread# 2, sequence# 0)
ORA-16240: Waiting for log file (thread# string, sequence# string)
Cause: Process is idle waiting for additional log file to be available.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
I dont understand why it's looking for sequence #0 after the flashback.
Thanks for the help.

Hello;
I hesitate to answer your question because you are not doing a good job of keeping the forum clean :
Total Questions: 13 (13 unresolved)
Please consider closing some of you old answered questions and rewarding those who helped you.
No action necessary.
Do you really have a thread 2? ( Redo thread number )
Quick check
select applied_scn,latest_scn from v$logstdby_progress;Use the DBA_LOGSTDBY_LOG View if you don't have a thread 2 then the sequence# is meaningless.
COLUMN DICT_BEGIN FORMAT A10;
SELECT FILE_NAME, SEQUENCE#, FIRST_CHANGE#, NEXT_CHANGE#,
TIMESTAMP, DICT_BEGIN, DICT_END, THREAD# AS THR# FROM DBA_LOGSTDBY_LOG
ORDER BY SEQUENCE#;Logical Standby questions are difficult, not a lot of them out there I'm thinking.
Check
http://docs.oracle.com/cd/E14072_01/server.112/e10700/manage_ls.htm
"Waiting On Gap State" ( However I still believe you don't have a 2nd thread# )
OR
http://psilt.wordpress.com/2009/04/29/simple-logical-standby/
Best Regards
mseberg
Edited by: mseberg on Apr 26, 2012 5:13 PM

Logical standby stuck at initializing SQL apply only coordinator process up

Hi
OS: solaris 5.10
Hardware: sun sparc
Oracle database: 11.2.0.1.0
Primary database name: asadmin
Standby database name: test
I had been trying to convert a physical standby to logical standby database. Both the primary and standby reside on the same machine.
The physical standby was created with a hot backup of primary.
I had been following document id 278371.1 to convert the physical to logical standby and used the following steps:
Relevant init parameters on primary:
*.db_name='asadmin'
*.db_unique_name='asadmin'
*.log_archive_config='dg_config=(asadmin,test)'
*.log_archive_dest_1='location=/u01/asadmin/archive valid_for=(all_logfiles,all_roles) db_unique_name=asadmin'
*.log_archive_dest_2='SERVICE=test async valid_for=(online_logfiles,primary_role) db_unique_name=test'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.fal_client='asadmin'
*.fal_server='test'
*.remote_login_passwordfile='EXCLUSIVE'
Relevant init parameters on standby database:
*.db_name='test' -- Was asadmin before I renamed the DB during conversion to logical standby
*.db_unique_name='test'
*.log_archive_dest_1='location=/u01/test/archive valid_for=(all_logfiles,all_roles) db_unique_name=test'
*.log_archive_dest_2='service=asadmin async valid_for=(online_logfiles,primary_role) db_unique_name=asadmin'
*.log_archive_dest_state_1=enable
*.log_archive_dest_state_2=defer
*.remote_login_passwordfile='EXCLUSIVE'*.fal_server=test
*.fal_client=asadmin
Steps on primary:
1) alter system set log_archive_dest_state_2=defer;
2) shutdown immediate;
3) Made sure that the physical standby has applied all of the redo sent to it following the shutdown.
4) startup mount;
5) ALTER DATABASE BACKUP CONTROLFILE to '/home/oracle/control01.ctl';
6) ALTER SYSTEM ENABLE RESTRICTED SESSION;
7) ALTER DATABASE OPEN;
8) Verified that the supplemental logging is on.
9) ALTER SYSTEM ARCHIVE LOG CURRENT;
10) Checked for the checkpoint change no. at this point which is 72403818 and is present in archive log file 1_62_775102253.dbf
11) EXECUTE DBMS_LOGSTDBY.BUILD;
12) ALTER SYSTEM ARCHIVE LOG CURRENT;
13) Checked for the archive log containing dictionary build which is 1_64_775102253.dbf
14) ALTER SYSTEM DISABLE RESTRICTED SESSION;
Details of archive logs and related checkpoint change nos:
NAME FIRST_CHANGE# NEXT_CHANGE#
/u01/asadmin/archive/1_61_775102253.dbf 72402901 72403817
/u01/asadmin/archive/1_62_775102253.dbf 72403817 72404069
/u01/asadmin/archive/1_63_775102253.dbf 72404069 72404211
/u01/asadmin/archive/1_64_775102253.dbf 72404211 72405700
Steps on standby:
1) shutdown immediate;
2) Copy the archivelog file 61(was created at primary after apply stopped at standby), 62(contains checkpoint no. 72403818), 63 and 64(contains dictionary build). Copy the backup controlfile from step 5 above to the controlfile location in standby init.
3) startup mount;
4) Rename all datafiles and redo log files (including standby redo log files) to the correct path on standby.
5) alter database recover automatic from '/u01/test/archive' until change 72405700 using backup controlfile; -- This completed error-free
6) alter database guard all; -- this completed error free
7) alter database open resetlogs; -- this completed error free.
8) nid target=sys/oracle12 dbname=test
9) Changed the db_name in init file to new name test.
10) Added a tempfile to temp tablespaces.
11) ALTER DATABASE REGISTER LOGICAL LOGFILE '/u01/test/archive/1_61_775102253.dbf'; -- ORA-16225: Missing LogMiner session name for Streams
12) ALTER DATABASE START LOGICAL STANDBY APPLY INITIAL 72405700; -- This completed error free.
Also enabled the log_archive_dest_state_2 on primary.
After this output from some views:
SQL> SELECT SESSION_ID, STATE FROM V$LOGSTDBY_STATE;
SESSION_ID STATE
1 INITIALIZING
SQL> SELECT SID, SERIAL#, SPID, TYPE FROM V$LOGSTDBY_PROCESS;
SID SERIAL# SPID TYPE
587 22 15476 COORDINATOR
SELECT PERCENT_DONE, COMMAND
FROM V$LOGMNR_DICTIONARY_LOAD
WHERE SESSION_ID = (SELECT SESSION_ID FROM V$LOGSTDBY_STATE);
PERCENT_DONE
COMMAND
0
SQL> SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
TYPE HIGH_SCN STATUS
COORDINATOR ORA-16111: log mining and apply setting up
SQL> SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN NEWEST_SCN
72405700 72411501
SELECT THREAD#, SEQUENCE#, FILE_NAME FROM DBA_LOGSTDBY_LOG L
WHERE NEXT_CHANGE# NOT IN
(SELECT FIRST_CHANGE# FROM DBA_LOGSTDBY_LOG WHERE L.THREAD# = THREAD#)
ORDER BY THREAD#,SEQUENCE#;
no rows selected
SQL> SELECT EVENT_TIME, STATUS, EVENT
FROM DBA_LOGSTDBY_EVENTS
ORDER BY EVENT_TIMESTAMP, COMMIT_SCN; 2 3
EVENT_TIME STATUS EVENT
14-FEB-12 02:00:50 ORA-16111: log mining and apply setting up
14-FEB-12 02:00:50 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 02:20:11 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 02:20:39 ORA-16111: log mining and apply setting up
14-FEB-12 02:20:39 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 02:54:15 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 02:57:38 ORA-16111: log mining and apply setting up
EVENT_TIME STATUS EVENT
14-FEB-12 02:57:38 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 03:01:36 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 03:13:44 ORA-16111: log mining and apply setting up
14-FEB-12 03:13:44 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 04:32:23 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 04:34:17 ORA-16111: log mining and apply setting up
14-FEB-12 04:34:17 Apply LWM 72405699, HWM 72405699, SCN 72405699
EVENT_TIME STATUS EVENT
14-FEB-12 04:36:16 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 04:36:21 ORA-16111: log mining and apply setting up
14-FEB-12 04:36:21 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 05:15:22 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 05:15:29 ORA-16111: log mining and apply setting up
14-FEB-12 05:15:29 Apply LWM 72405699, HWM 72405699, SCN 72405699
I also greped for lsp and lcr processes and found that lsp is up but do not see any lcr.
The logs are getting transported to the archive destination on standby whenever they are archived on primary but are not getting applied to standby.
Also in case the standby is down while a log is generated on primary it is not automatically transported to standby once the standby is up, means gap resolution is also not working.
I see the following in alert log every time I try to restart the log apply, everything seems to be stuck at initialization.
ALTER DATABASE START LOGICAL STANDBY APPLY (test)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
Tue Feb 14 05:15:28 2012
LSP0 started with pid=28, OS id=23391
Completed: alter database start logical standby apply immediate
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 0, ResetLogScn 0
-- NOTHING AFTER THIS

Hello;
I noticed some of your parameters seem to be wrong.
fal_client - This is Obsolete in 11.2
You have db_name='test' on the Standby, it should be 'asadmin'
fal_server=test is set like this on the standby, it should be 'asadmin'
I might consider changing VALID_FOR to this :
VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)Would review 4.2 Step-by-Step Instructions for Creating a Logical Standby Database of Oracle Document E10700-02
Document 278371.1 is showing its age in my humble opinion.
-----Wait on this until you fix your parameters----------------------
Try restarting the SQL Apply
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEI don't see the parameter MAX_SERVERS, try setting it to 8 times the number of cores.
Use these statements to trouble shoot :
SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS;
SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME LIKE ;TRANSACTIONS%';
SELECT COUNT(1) AS IDLE_PREPARERS FROM V$LOGSTDBY_PROCESS WHERE
TYPE = 'PREPERER' AND STATUS_CODE = 16166;Best Regards
mseberg
Edited by: mseberg on Feb 14, 2012 7:37 AM

Sql Apply issue in logical standby database--(10.2.0.5.0) x86 platform

Hi Friends,
I am getting the following exception in logical standby database at the time of Sql Apply.
After run the command alter database start logical standby apply sql apply services start but after few second automatically stop and getting following exception.
alter database start logical standby apply
Tue May 17 06:42:00 2011
No optional part
Attempt to start background Logical Standby process
LOGSTDBY Parameter: MAX_SERVERS = 20
LOGSTDBY Parameter: MAX_SGA = 100
LOGSTDBY Parameter: APPLY_SERVERS = 10
LSP0 started with pid=30, OS id=4988
Tue May 17 06:42:00 2011
Completed: alter database start logical standby apply
Tue May 17 06:42:00 2011
LOGSTDBY status: ORA-16111: log mining and apply setting up
Tue May 17 06:42:00 2011
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 4, Transaction Chunk Size = 201
LOGMINER: Memory Size = 100M, Checkpoint interval = 500M
Tue May 17 06:42:00 2011
LOGMINER: krvxpsr summary for session# = 1
LOGMINER: StartScn: 0 (0x0000.00000000)
LOGMINER: EndScn: 0 (0x0000.00000000)
LOGMINER: HighConsumedScn: 2660033 (0x0000.002896c1)
LOGMINER: session_flag 0x1
LOGMINER: session# = 1, preparer process P002 started with pid=35 OS id=4244
LOGSTDBY Apply process P014 started with pid=47 OS id=5456
LOGSTDBY Apply process P010 started with pid=43 OS id=6484
LOGMINER: session# = 1, reader process P000 started with pid=33 OS id=4732
Tue May 17 06:42:01 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1417, X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
Tue May 17 06:42:01 2011
LOGMINER: Turning ON Log Auto Delete
Tue May 17 06:42:01 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
Tue May 17 06:42:01 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1418, X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
LOGSTDBY Apply process P008 started with pid=41 OS id=4740
LOGSTDBY Apply process P013 started with pid=46 OS id=7864
LOGSTDBY Apply process P006 started with pid=39 OS id=5500
LOGMINER: session# = 1, builder process P001 started with pid=34 OS id=4796
Tue May 17 06:42:02 2011
LOGMINER: skipped redo. Thread 1, RBA 0x00058a.00000950.0010, nCV 6
LOGMINER: op 4.1 (Control File)
Tue May 17 06:42:02 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1419, X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1420, X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1421, X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
LOGSTDBY Analyzer process P004 started with pid=37 OS id=5096
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
LOGSTDBY Apply process P007 started with pid=40 OS id=2760
Tue May 17 06:42:03 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
LOGSTDBY Apply process P012 started with pid=45 OS id=7152
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1422, X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1423, X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
Tue May 17 06:42:03 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1424, X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
LOGMINER: session# = 1, preparer process P003 started with pid=36 OS id=5468
Tue May 17 06:42:03 2011
LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
Tue May 17 06:42:04 2011
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1425, X:\TANVI\ARCHIVE2\ARC01425_0748170313.001
LOGSTDBY Apply process P011 started with pid=44 OS id=6816
LOGSTDBY Apply process P005 started with pid=38 OS id=5792
LOGSTDBY Apply process P009 started with pid=42 OS id=752
Tue May 17 06:42:05 2011
krvxerpt: Errors detected in process 34, role builder.
Tue May 17 06:42:05 2011
krvxmrs: Leaving by exception: 600
Tue May 17 06:42:05 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
LOGSTDBY status: ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
Tue May 17 06:42:06 2011
Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_lsp0_4988.trc:
ORA-12801: error signaled in parallel query server P001
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
Tue May 17 06:42:06 2011
LogMiner process death detected
Tue May 17 06:42:06 2011
logminer process death detected, exiting logical standby
LOGSTDBY Analyzer process P004 pid=37 OS id=5096 stopped
LOGSTDBY Apply process P010 pid=43 OS id=6484 stopped
LOGSTDBY Apply process P008 pid=41 OS id=4740 stopped
LOGSTDBY Apply process P012 pid=45 OS id=7152 stopped
LOGSTDBY Apply process P014 pid=47 OS id=5456 stopped
LOGSTDBY Apply process P005 pid=38 OS id=5792 stopped
LOGSTDBY Apply process P006 pid=39 OS id=5500 stopped
LOGSTDBY Apply process P007 pid=40 OS id=2760 stopped
LOGSTDBY Apply process P011 pid=44 OS id=6816 stopped
Tue May 17 06:42:10 2011

Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []submit an SR to ORACLE SUPPORT.
refer these too
*ORA-600/ORA-7445 Error Look-up Tool [ID 153788.1]*
*Bug 6022014: ORA-600 [KRVXBPX20] ON LOGICAL STANDBY*

Doubt regarding switchover from logical standby to primary

I am using Oracle 10g databases on Linux environment
I was trying creating a data guard configuration and once I was successfully done I created a logical standby database from the physical standby . Then I was trying to do a switchover .
By mistake I gave the prepare switchover command in the logical standby before executing it in the primary . And then when I gave it in the primary both the status turned to be "PREPARING SWITCHOVER"
In logical standby
SQL> ALTER DATABASE PREPARE TO SWITCHOVER TO PRIMARY;
Database altered.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
PREPARING SWITCHOVER
In primary
SQL> ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY;
Database altered.
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
PREPARING SWITCHOVERNow I am not able to commit any of them to primary or logical standby
In primary
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY;
ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY
ERROR at line 1:
ORA-16217: prepare to switchover has not completed
ORA-06512: at line 1
In logical standby
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
ALTER DATABASE commit TO SWITCHOVER TO PRIMARY
ERROR at line 1:
ORA-16109: failed to apply log data from previous primaryLet me know what should be done now ? Is there anyway to solve this issue ?

Can you try using the following first on Primary and then on Standby?
ALTER DATABASE PREPARE TO SWITCHOVER CANCEL;

Deadlock error on logical standby

Similar Messages

Maybe you are looking for