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

Similar Messages

Audit DBA Activity, skip table from logical standby!

Dear All,
My database is 10gR2 on windows 2003 server.
I want to know if I can put some audit on the commands: execute dbms_logstdby.skip() to skip tables from Logical standby and also the same on unskipping the objects exec dbms_logstdby.unskip.
Thanks, Imran

Hi,
Given that your Database is 10g, the auditing options were extended to included DML from only SELECT in 9i, but not audit on procedures. You could double check the Fine Grained Auditing options in 10g, but I don't think this extends to DBMS_ packages.
I would consider writing a trigger or a small job that monitors the DBA_LOGSTDBY_SKIP view for additional entries. This is the only workaround that I can suggest that might fit your needs.

Physical Standby from Logical Standby

Is it possible this scenario?
Create a physical standby from logical standby and the physical receive archive from logical.
I mean,
Primary (10g production) -> Logical (11gr2 new server 1) -> (Physical 11gr2 new server 2)
The goal of this scenario is a migration with a short downtime.
O.S. aix 6.1
11.2.0.2

Is it possible this scenario?YES

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

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

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.

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

Goldengate from physical standby with Active data guard or from logical standby - which is better?

Hi,
We have Oracle 11.2.0.4 and are currently using Active Data Guard on a physical standby. My boss wants me to use Goldengate
to replicate several schema from Oracle to SqlSserver. She doesn't want to touch the Primary, which is in production. Would it be better
to setup a Logical standby for Goldendate to use, in addition to the Physical standby? Or will it be sufficient to use the Physical standby?
The application tables don't all have primary keys. I'm trying to decide if the Logical standby adds another layer of complexity or would
introduce delays in getting the data from Oracle to Sqlserver.
Thanks in advance,

Hi,
In this case I recommend you to use physical standby + Golden gate with ALO mode. You might have sligthly more trouble in logical standby. it means you might have more trouble at Goldengate's extract side.
You said
The application tables don't all have primary keys.
so you have to add keycols on replicat side.
I recommend you to add an index which should consist of keycols columns. it will be necessary for replicat performance.
Best Regards

Archiving Error. from Primary & Standby Server. pls help.

Hi all.
Im currently getting error messages from both of my Primary and Standby Database. can anyone help me identify what error message would it be?
Primary Database:
Tue Apr 21 09:40:13 2009
Creating archive destination LOG_ARCHIVE_DEST_2: 'Standby'
ARC0: FAL archive, error 20 creating remote archivelog file 'Standby'
Tue Apr 21 09:40:14 2009
Errors in file /export/oradata/log/bdump/arc0_20901.trc:
ORA-00020: maximum number of processes () exceeded
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Tue Apr 21 09:40:14 2009
ORACLE Instance - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Tue Apr 21 09:40:14 2009
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
Tue Apr 21 09:40:14 2009
Errors in file /export/oradata/log/bdump/arc0_20901.trc:
ORA-16055: FAL request rejected
Tue Apr 21 09:40:40 2009
Thread 1 advanced to log sequence 41971
Current log# 1 seq# 41971 mem# 0: /export/oradata/logfile/redoMIBS01a.log
Current log# 1 seq# 41971 mem# 1: /export/oradata/logfile/redoMIBS01b.log
Tue Apr 21 09:40:40 2009
ARC1: Evaluating archive log 4 thread 1 sequence 41970
ARC1: Beginning to archive log 4 thread 1 sequence 41970
Creating archive destination LOG_ARCHIVE_DEST_1: '/export/oradata/MIBS/archive/log00010001S0000041970.ARC'
ARC1: Completed archiving log 4 thread 1 sequence 41970
Tue Apr 21 09:41:40 2009
Errors in file /export/oradata/log/bdump/arc0_20901.trc:
ORA-00020: maximum number of processes () exceeded
Standby Database:
Tue Apr 21 09:36:10 2009
RFS: Possible network disconnect with primary database
Closing latent archivelog for thread 1 sequence 41687
EOF located at block 40958 low SCN 0:123821645 next SCN 0:123821645
Latent archivelog '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041687.ARC'
If you wish to failover to this standby database, you should use the
following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGFILE '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041687.ARC';
Tue Apr 21 09:36:10 2009
Errors in file /export/oradata/log/udump/mibs_rfs_3802.trc:
ORA-00367: checksum error in log file header
ORA-00311: cannot read header from archived log
ORA-00334: archived log: '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041687.ARC'
ORA-27091: skgfqio: unable to queue I/O
ORA-27072: skgfdisp: I/O error
SVR4 Error: 22: Invalid argument
Additional information: 1
Tue Apr 21 09:36:19 2009
RFS: Possible network disconnect with primary database
Closing latent archivelog for thread 1 sequence 41688
EOF located at block 2677 low SCN 0:123821835 next SCN 0:123821835
Latent archivelog '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041688.ARC'
If you wish to failover to this standby database, you should use the
following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGFILE '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041688.ARC';
Tue Apr 21 09:36:19 2009
Errors in file /export/oradata/MIBS/log/udump/mibs_rfs_3807.trc:
ORA-00367: checksum error in log file header
ORA-00311: cannot read header from archived log
ORA-00334: archived log: '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041688.ARC'
ORA-27091: skgfqio: unable to queue I/O
ORA-27072: skgfdisp: I/O error
SVR4 Error: 2: No such file or directory
Additional information: 1
Really2 needing anyone's help at this point.

Hi..
Errors in file /export/oradata/log/bdump/arc0_20901.trc:ORA-00020: maximum number of processes () exceeded>
What is the value of the parameter PROCESSES.You need to increase the value which would require bouncing the database.Increaing the Processes parameter requires increase in session parameter too.
Sessions = (1.1 * PROCESSES) + 5
[http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams169.htm]
[http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams191.htm]
HTH
Anand

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.

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

Skip the DELETE command on logical standby

Hi All,
I want to skip the DELETE command on logical standby.
DB Version - 10.2
OS - Linux
Primary DB and logical standby DB .
In our DB schema some transaction tables. We delete data from those tables by delete commands.
Delete command, also delete data from logical standby DB. But we want to skip on logical standby DB .
I use following for that and get error.
ALTER DATABASE STOP LOGICAL STANDBY APPLY;
EXECUTE DBMS_LOGSTDBY.SKIP (stmt =>'DELETE TABLE', schema_name =>'TEST',object_name =>'TRANS',proc_name => null);
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
But I got error
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00306: wrong number or types of arguments in call to 'SKIP'
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
When I change stmt =>'DELETE TABLE' to stmt =>'DML', no error happen
Please help me to solve this issue . This is urgent.
Thanks in advance.
Regards

Dear aditi2,
Actually it is so simple to understand the problem. Please read the following documentation and try to understand the SKIP procedure.
http://download.oracle.com/docs/cd/B14117_01/appdev.101/b10802/d_lsbydb.htm#997290
*SKIP Procedure*
Use the SKIP procedure to define filters that prevent the application of SQL statements on the logical standby database.
By default, all SQL statements executed on a primary database are applied to a logical standby database.
If only a subset of activity on a primary database is of interest for application to the standby database,
you can use the SKIP procedure to define filters that prevent the application of SQL statements on the logical standby database.
While skipping (ignoring) SQL statements is the primary goal of filters,
it is also possible to associate a stored procedure with a DDL filter so that runtime determinations can be made whether to skip the statement,
execute this statement, or execute a replacement statement.
Syntax
DBMS_LOGSTDBY.SKIP (
     stmt                      IN VARCHAR2,
     schema_name               IN VARCHAR2,
     object_name               IN VARCHAR2,
     proc_name                 IN VARCHAR2,
     use_like                  IN BOOLEAN,
     esc                       IN CHAR1);Hope That Helps.
Ogan
Edited by: Ogan Ozdogan on 30.Tem.2010 13:03

[Logical Standby] Which table/SQL caused paging-out

We have a Primary-Logical DR configuration.
Recently, it has a problem with the logical: it's continuously paging out data from some transactions:
SELECT SUBSTR(name, 1, 40) AS NAME, SUBSTR(value,1,32) AS VALUE FROM GV$LOGSTDBY_STATS;
number of preparers     3
number of appliers     18
maximum SGA for LCR cache     4095
parallel servers in use     24
maximum events recorded     1000000
preserve commit order     TRUE
transaction consistency     FULL
record skip errors     Y
record skip DDL     Y
record applied DDL     N
record unsupported operations     Y
coordinator state     IDLE
transactions ready     7
transactions applied     0
coordinator uptime     9646
realtime logmining     Y
apply delay     0
Log Miner session ID     1
txns delivered to client     1068651
DML txns delivered     1017135
DDL txns delivered     15
CTAS txns delivered     0
Recursive txns delivered     51501
Rolled back txns seen     23463
LCRs delivered to client     11682189
bytes of redo processed     14475529508
bytes paged out     1482524624
seconds spent in pageout     8922
bytes checkpointed     0
seconds spent in checkpoint     0
bytes rolled back     7500032
seconds spent in rollback     90
seconds system is idle     0
SELECT SID, SERIAL#, SPID, TYPE, HIGH_SCN, STATUS_CODE, STATUS
FROM GV$LOGSTDBY_PROCESS
ORDER BY TYPE, SPID;
ANALYZER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
APPLIER     16116     ORA-16116: no work available
BUILDER     16243     ORA-16243: paging out 4752 bytes of memory to disk
COORDINATOR     16116     ORA-16116: no work available
PREPARER     16127     ORA-16127: stalled waiting for additional transactions to be applied
PREPARER     16127     ORA-16127: stalled waiting for additional transactions to be applied
PREPARER     16127     ORA-16127: stalled waiting for additional transactions to be applied
READER     16127     ORA-16127: stalled waiting for additional transactions to be applied
select xidusn, xidslt, xidsqn, count(*) from system.logmnr_spill$
group by xidusn, xidslt, xidsqn;
996     46     249     254
710     37     838     825
623     3     706     254
478     7     42564     254
765     38     649     824
42     6     415494     3729
264     35     4817     3738
How can we identify the table/SQL to skip & instantiate it later so the logical DB will not being lag far behind.
Thank you.

Hi,
Best way to find SQL is to mine the current archive log getting applied on standby and check for the SQL, you might not get the exact SQL, but you will get the object which is getting updated.
Or
You can use AWR report from logical standby of this time to find the update statement which is resource extensive.
There is no way to find the exact SQL on primary which is causing the issue on standby.
Regards
Anudeep

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.

Logical Standby databases

Hi,
When we say "Logical Standby Databases are logically identical to primary databases although the physical organization and structure of the data can be different." what does it exactly means?
Does it mean that in logical standby tablespace name, schema name, table name, column names etc can be different and still has the same data as primary?
Does it mean that we can exclude indexes and constraints as present in primary?
Only the data should match with primary word by word, value by value?
I am asking this as i have never worked in a logical standby database but i seriously want to know.
Please answer.
Regards,
SID

Physical standby differs from logical standby:
Physical standby schema matches exactly the source database.
Archived redo logs and FTP'ed directly to the standby database which is always running in "recover" mode. Upon arrival, the archived redo logs are applied directly to the standby database.
Logical standby is different from physical standby:
Logical standby database does not have to match the schema structure of the source database.
Logical standby uses LogMiner techniques to transform the archived redo logs into native DML statements (insert, update, delete). This DML is transported and applied to the standby database.
Logical standby tables can be open for SQL queries (read only), and all other standby tables can be open for updates.
Logical standby database can have additional materialized views and indexes added for faster performance.
Installing Physical standbys offers these benefits:
An identical physical copy of the primary database
Disaster recovery and high availability
High Data protection
Reduction in primary database workload
Performance Faster
Installing Logical standbys offer:
Simultaneous use for reporting, summations and queries
Efficient use of standby hardware resources
Reduction in primary database workload
Some limitations on the use of certain datatypes

Error from Logical Standby

Similar Messages

Maybe you are looking for