ORA-28015
ACCOUNT UNLOCK attempted on standby database while there is a conflicting ACCOUNT LOCK status on the primary database.
Cause
An attempt to unlock an account on a standby database was prevented because the account was previously marked as locked on the primary database. All attempts to unlock the account on the standby database will be prevented as long as the overriding ACCOUNT LOCK condition exists on the primary database.
Action
If this database is part of an Oracle Data Guard configuration, perform the ACCOUNT UNLOCK action on the primary database. If this database is read-only, then set the database to read/write and perform the ACCOUNT UNLOCK action.
ORA-28015
account unlock attempted on read-only database but a conflicting account lockout on the primary exists
Cause
An attempt to unlock an account on a read-only database was prevented, because the account was previously marked as locked on the primary database. All attempts to unlock the account on the read-only database will be prevented as long as the overriding "account locked" condition exists at the primary database.
Action
If this database is part of a Data Guard configuration, perform the account unlock action on the primary database. If this database is read-only, then set the database to read/write and perform the account unlock action.
ORA-28015
account unlock attempted on read-only database but a conflicting account lockout on the primary exists
Cause
An attempt to unlock an account on a read-only database was prevented, because the account was previously marked as locked on the primary database. All attempts to unlock the account on the read-only database will be prevented as long as the overriding "account locked" condition exists at the primary database.
Action
If this database is part of a Data Guard configuration, perform the account unlock action on the primary database. If this database is read-only, then set the database to read/write and perform the account unlock action.
