Ora 16191 Primary Log Shipping Client Not Logged On Standby

Ora 16191 Primary Log Shipping Client Not Logged On Standby – On node asm1 there is database orcl using asm. An attempt to ship redo to standby without logging on to standby or with invalid user. After rebuilding logical standby, primary throwing below error and log shipping was not happening. I have regenerated these files for both primary and standby databases several times using the same password, i can connect as sys/password to both primary.

Primary log shipping client not logged on standby cause: Primary log shipping client not logged on standby. Primary log shipping client not logged on standby. There was password file and both primary and standby databases and they had same passwords.

Ora 16191 Primary Log Shipping Client Not Logged On Standby

Error 16191 creating remote archivelog file 'ebsodr_s2' arc0: For reasons unknown, when the primary and standby. Monitor alert log and make sure archive logs are applying fine at standby side.

If the password file is missing, then create it with ignorecase=y option as follows. Primary log shipping client not logged on standby the root cause of the problem turned out to be a bug in the cisco firewall. Sql> alter system set events ‘16191 trace name errorstack level 10’;

Primary log shipping client not logged on standby fal[server, arc0]: An attempt to ship redo to standby without logging on to standby or with invalid user credentials. Primary log shipping client not logged on standby.

I created orapw$ {oracle_sid} on. I have two nodes asm1 & asm2 with rhel4 u5 os. Error is reported on primary db, so lets set trace in primary (not standby) primary:

Oracle19cADG报错ORA16191 墨天轮