ORA-20600: The specified target is in the process of being deleted

Recived the following error while adding a database(which was removed earlier)through Oracle Grid Control 10.2.0.5.

Database Instance Configuration Result
TESTA:
java.sql.SQLException: ORA-20600: The specified target is in the process of being deleted.(target name = TESTA)(target type = oracle_database)(target guid = 48BA0AB2565D68E6437E6F5062A7426F) ORA-06512: at "SYSMAN.TARGETS_INSERT_TRIGGER", line 46 ORA-04088: error during execution of trigger 'SYSMAN.TARGETS_INSERT_TRIGGER' ORA-06512: at "SYSMAN.EM_TARGET", line 2117 ORA-06512: at "SYSMAN.MGMT_TARGET", line 2701 ORA-06512: at line 1


SQL> select TARGET_NAME from mgmt_targets_delete;

TARGET_NAME
-----------
TESTA


The above entry needs to be deleted.For the purose we tried executing the below script, which resulted in an error.

SQL> begin
2 mgmt_admin.delete_target('TESTA','oracle_database');
3 end;
4 /
begin
*
ERROR at line 1:
ORA-20206: Target does not exist:
ORA-06512: at "SYSMAN.MGMT_ADMIN", line 462
ORA-06512: at "SYSMAN.MGMT_ADMIN", line 624
ORA-06512: at line 2

After some google search we could find another proc to achieve the required.

SQL> begin
2 mgmt_admin.delete_target_internal('TESTA','oracle_database');
3 end;
4 /

PL/SQL procedure successfully completed.

SQL>


Once this was done, we were able to add a new database Grid Control Target.

Convert Standby Database to independent operational DB

We had a requirement to convert the existing standby database to an independent one.

This is the steps that we followed to achieve this.

1.Shutdown the primary database consistently.

2.Do a failover on the standby database by issuing the following command.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH FORCE;

Database altered.

SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WAIT WITH SESSION SHUTDOWN;

Database altered.

SQL> alter database open ;

Database altered.

In the primary database comment/remove the following parameters:

*.log_archive_config
*.log_archive_dest_2
*.log_archive_dest_state_2='ENABLE'
*.dg_broker_start
*.standby_file_management

The above changes would prevent the log shipping to old standby database and dataguard brocker wont start.

If the "*.dg_broker_start" parameter is set to true, expect the following error while opening the database.

ORA-16649: possible failover to another database prevents this database from
being opened

Once the above changes are made, the database could be started independently.

ORA - 17628

Was recieving the following error during the creation of the standby database on 11.2 Oracle Database.

RMAN-00571: ==================================================
RMAN-00569: ====== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ==================================================
RMAN-03002: failure of Duplicate Db command at 06/07/2011 14:07:03
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on prmy1 channel at 06/07/2011 14:07:03
ORA-17628: Oracle error 19505 returned by remote Oracle server

Check the alert log file at standby location.The software will be trying to access/write into an non-existent directory.

Resolution:
Create the directory and give the read/write permission.

RMAN Error 04014

I was recieving the below error while creating stand by database through RMAN.

RMAN-04014: startup failed: ORA-01261: Parameter db_create_file_dest destination string cannot be translated

The value of parameter db_create_file_dest locaiton was proper and was present at both the source and destination servers with proper files permissions.

But the issue later turned out to be because of an improper settting of another parameter -control_files, which had a extra character added to it(yes ..by mistake).Anyway the issue was with the improper location setting.