Mani's Blog

September 27, 2012

Oracle Agent stopped working : ORA-12505: TNS:listener does not currently know

Filed under: Uncategorized — mani @ 11:03 pm

Oracle Agent stopped working all of sudden.

Agent stop populating to grid. Stopped, Did clearstate, restarted agent. Nothing worked.

Tried following steps too, but no help.

1 stop the agent
2 delete agntstmp.txt and lastupld.xml (under sysman/emd)
3 Delete all the files under upload and collection directories
4 start the agent
Here it is a real solution.

Go to Grid Control,
Click on Setup
Choose Agents
Choose the Problematic Agent
Click on Unlock.
Resynchronize the agent.

 

 

September 20, 2012

ORA-16792: configurable property value is inconsistent with database setting

I have DG broker configured on stand-alone database servers (primary and standby).  After I migrated standby database to new ASM diskgroup I ran into issue “Warning: ORA-16608: one or more databases have warnings” and “ORA-16792: configurable property value is inconsistent with database setting”

Restarting the Data guard broker fixed the issue.

DGMGRL> show configuration

Configuration
Name:                contact
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodbcntdg – Primary database
xnodbcnt   – Physical standby database

Fast-Start Failover: DISABLED

Current status for “contact”:
Warning: ORA-16608: one or more databases have warnings

DGMGRL> show database xnodbcnt

Database
Name:            xnodbcnt
Role:            PHYSICAL STANDBY
Enabled:         YES
Intended State:  APPLY-ON
Instance(s):
XNODBCNT

Current status for “xnodbcnt”:
Warning: ORA-16792: configurable property value is inconsistent with database setting

I just restarted as below.

 

SQL> alter system set dg_broker_start=false scope=both;

System altered.

SQL> alter system set dg_broker_start=true scope=both;

System altered.

SQL>

Then the issue is gone.

 

DGMGRL> show database xnodbcnt

Database
Name:            xnodbcnt
Role:            PHYSICAL STANDBY
Enabled:         YES
Intended State:  APPLY-ON
Instance(s):
XNODBCNT

Current status for “xnodbcnt”:
SUCCESS

DGMGRL>

September 17, 2012

Warning: ORA-16607: one or more databases have failed Error: ORA-16816: incorrect database role

Filed under: Data Guard Broker,Database,Dataguard,Oracle — mani @ 10:01 pm
Tags:

I have Data guard broker configured on my Primary and Standby database servers.  For some reason we had to failover using SQL commnad (didn’t use DG manager).  Later on dgmgrl shows errors as below.

DGMGRL> show configuration

Configuration
Name:                CONTACT
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
XNODBCNT   – Primary database
XNODBCNTDG – Physical standby database

Fast-Start Failover: DISABLED

Current status for “CONTACT”:
Warning: ORA-16607: one or more databases have failed

DGMGRL> show database ‘XNODBCNT’

Database
Name:            XNODBCNT
Role:            PRIMARY
Enabled:         YES
Intended State:  TRANSPORT-ON
Instance(s):
XNODBCNT

Current status for “XNODBCNT”:
Error: ORA-16816: incorrect database role

Solution: I tried many thing like enabling/disabling configuration, database and other nothing helped,  I had reconfigure it again as below to make DG broker to work properly.

DGMGRL> create configuration CONTACT as primary database is XNODBCNTDG connect identifier is xnodbcntdg;
Configuration “contact” created with primary database “xnodbcntdg”
DGMGRL> add database XNODBCNT as connect identifier is xnodbcnt maintained as physical;
Database “xnodbcnt” added
DGMGRL> show configuration;

Configuration
Name:                contact
Enabled:             NO
Protection Mode:     MaxPerformance
Databases:
xnodbcntdg – Primary database
xnodbcnt   – Physical standby database

Fast-Start Failover: DISABLED

Current status for “contact”:
DISABLED

DGMGRL> enable configuration
Enabled.
DGMGRL> show configuration verbose

Configuration
Name:                contact
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodbcntdg – Primary database
xnodbcnt   – Physical standby database

Fast-Start Failover: DISABLED

Current status for “contact”:
Warning: ORA-16610: command “EDIT DATABASE xnodbcnt SET PROPERTY” in progress

DGMGRL> show configuration verbose

Configuration
Name:                contact
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodbcntdg – Primary database
xnodbcnt   – Physical standby database

Fast-Start Failover: DISABLED

Current status for “contact”:
SUCCESS

DGMGRL>

Blog at WordPress.com.