Thursday, August 23, 2012

EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..

Due to communication between OMS and agent does not work. This is in most cases because something has been changed to one of the components so the SSL certificate is not valid anymore. Therefore you have to resecure the agent. Your last try shows the error that you have used the wrong password for registration
Then go to the agent and do the following:
- emctl stop agent
- delete all files in
$AGENT_HOME/sysman/emd
rm agntstmp.txt
$AGENT_HOME/sysman/emd/upload and
rm -rf *
$AGENT_HOME/sysman/emd/state
rm -rf *
- emctl clearstate agent (this should delete all state files but sometimes it is not enough, but I experienced that it is better to use this command after deletion of the files)
- emctl secure agent (and specify the password on demand)
- emctl start agent

This should solve your problem.

Incase if you still have any issues in starting the agent or uploading files is not getting processed then look into the below:

Login to EM Console --> Setup -->Agents  -->
Misconfiguration Alerts and Blocked Agents

and check whether the server is blocked or not if it is blocked unblock it and then try the below:

./emctl clearstate agent
./emctl upload agent
./emctl status agent


Friday, August 3, 2012

If db_recovery_file_dest_size got full

Mostly this is applicable for 11g Instances when ever the db_recovery_file_dest_size got full then database will be in hang state and unable to operate anything.

SQL> show parameter recovery
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest                string      /u01/oradata/xxqa/arch
db_recovery_file_dest_size           big integer 120G
recovery_parallelism                 integer     0

SQL> select * from v$flash_recovery_area_usage;

FILE_TYPE            PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
-------------------- ------------------ ------------------------- ---------------
CONTROL FILE                          0                         0               0
REDO LOG                              0                         0               0
ARCHIVED LOG                      53.31                         0             250
BACKUP PIECE                          0                         0               0
IMAGE COPY                            0                         0               0
FLASHBACK LOG                         0                         0               0
FOREIGN ARCHIVED LOG                  0                         0               0

RMAN> crosscheck archivelog all;

RMAN> list expired archivelog all;

Note: Above command will give the list of expired archive logs.

RMAN> delete expired archivelog all;
Note: Above command will delete the expired archive logs.

Once after deleting the expired archivelogs again check usage from the below query and make sure space has been released.

SQL> select * from v$flash_recovery_area_usage;