Old alert logs

Good Morning,
Just a quick question about the old alert logs on the home page of the oem. They have been sitting there for a while and I would like to delete them. Is there a way to go about doing this?
Thanks in advance.
regards,
al

A,
For most of the alerts in EM-GC, the main way to clear the alerts is to resolve the underlying issue. For example, if you get a filesystem utilization alert, then if you free up more space, then the next time the Agent checks the space against the thresholds, if the space used does not cross the thresholds, then the filesystem utilization alert will clear. There are also a subset of alerts (e.g. log-based alerts such as alert log) that will allow the user to manually 'clear' the alerts from the EM-GC console. If you do not care about getting alerts for the metric, then you can remove the thresholds from the metric to prevent the generation of alerts for that metric.
If You are pretty sure that the underlying cause is cleared and the alert stucked in GC Repository you may need to log a new SR it could be a bug.
Regarding Deleting the alerts manually from the repository this is very dangerous and it may has a bad impact on the consistency of the data.
also deleting the alert manually from OEM-DBconsole is completely different than Grid Control R2.
Note: OEM-DBconsole = OEM-GC R1 (Utilize The Same Repository)
Regards,
MettoMorPhisM

Similar Messages

Alert log file of the database is too big

Dear Experts?
Let me update you that we are in process of doing an R12.1 upgrade ? And Our Current Instance is running on the 11.5.10 with 9.2.0.6 ?
We have the below challenges before going for an database upgrade ?
We have observed that the customer database alert_SID.log (9.2.0.6) size is 2.5GB ? how to purge this file ? Please advise
Please also note that our Instance is running on the Oracle Enterprise Linux 4 update 8
Regards
Mohammed.

user977334 wrote:
Dear Experts?
Let me update you that we are in process of doing an R12.1 upgrade ? And Our Current Instance is running on the 11.5.10 with 9.2.0.6 ?
We have the below challenges before going for an database upgrade ?
We have observed that the customer database alert_SID.log (9.2.0.6) size is 2.5GB ? how to purge this file ? Please advise
Please also note that our Instance is running on the Oracle Enterprise Linux 4 update 8
Regards
Mohammed.Rename the alert logfile. once you rename the logfile another alert log file will create and being populated with time, and later you can delete it old alert log file . it doesnot harm your database.
--neeraj

Drop database deletes the alert log

Hi DBA's ,
I ran into a strange situation i never faced before.
We have a Oracle database version 11.2.0.3.0.
This is dev db which i had to refresh from production via rman.
After the drop database command finished all the contents of my trace folder dissapered including the alert log.
Has anyone faced this situation before or help me understand what happened

himmy, if you are dropping the database why would you need the old alert.log or any other diagnostic directory files? Ideally if you drop a database there should be no record of it left on the system when the drop completes. Why is this a problem?
If you are refreshing the database from production then instead of dropping the database and creating a new database via rman restore perhaps you should be using either the export/import transportable tablespace feature to move the files or traditional export/import of the data.
HTH -- Mark D Powell --

Removed standby but getting interesting alert log entry

So, we had multiple set ups of primary database in our local data center, standby in remote location.
We're in the process of shutting down our remote location and have shut down our standbys gracefully, i.e., shutdown managed standby mode, removed archive_log_dest, changed archive_log_dest_state, etc. However, in some primary databases, I'm seeing a weird entry in the alert log:
Changing destination 2 from remote to local during archival of log#: 2 sequence#: 48708 thread#: 1
If I check my local destination, the archive log is created fine. In the remote location, no archives are being created.
I've not found anything on Google, Metalink, anywhere! Has anyone else seen this before, and if so, do I need to worry about it?
Oracle version is 11.1.0.7

Hello;
Its just information. You can ignore it.
Went back to some 2010 alert logs and found :
network reconnect abandoned
Attempting destination LOG_ARCHIVE_DEST_2 network reconnect
Setting 'active' archival for destination LOG_ARCHIVE_DEST_2Not much chance of finding here as all old version of Oracle are gone and a SAN move makes old alert logs rare. Still it just information or Oracle would throw an error.
Best Regards
mseberg
Edited by: mseberg on Jul 31, 2012 11:32 AM
Later
Tried to recreate message using several combinations of the parameters you listed. Unable to recreate, but only have 11.2.0.3.0 to test on.
Edited by: mseberg on Jul 31, 2012 12:44 PM

12c Cloud Control Alert Log Purge Error

I'm trying to purge old alert log events in EM 12c, but i'm getting error - The alert(s) could not be purged. Please ensure you have Edit privileges on this target while purging.
What's i'm doing wrong? Cant find anything close to this in EM documentation.
Thank you.

Hi,
What privileges do you have on the target? You'll need at least Manage Target Events (a subprivilege of Operator) in order to clear events on the target.
regards,
Ana

Seeking comments about managing Oracle's Alert log

Good morning,
Alert logs can often be very useful.
I am forming the opinion that it would probably be a good idea to keep a backup of the alert logs for, maybe, a 3 to 6 months sliding window.
I would like to know the views of the forum members on the subject of alert log backups, including how long the backups (if any) are kept. Actual practice on the subject in production environments is greatly appreciated.
Thank you for taking the time to comment on the subject,
John.

Hello Asif,
>
Yes , may be you need to open a SR in metalink and they may ask something old incident. For this reason you need to check the old alert log content. That's why I suggest to keep the alert log for production environment for 3/4 years.
>
I had not thought about someone asking for an incident that would be over a year old but, I can see that on occasion having the records might be useful.
>
Now a days storage are cheap so it's not that critical to store the alert log files.
>
I completely agree. I was more concerned about managing that many logs... on the other, they are just flat files, not that hard to manage.
Thank you,
John.

Change of date in alert log

Hi
Oracle Version 10.2.0.3.0
Last friday we had a power failure and a server rebooted abruptly. After it came online I restarted the database and the db did a instance recovery and came online without any problems. However when I checked the alert log file I noticed that the date & timestamp has gone back 14 days. This was there for a while and then it started showing the current date & timestamp. Is that normal? If it's not could some one help me to figure out why this has happened?
Fri Feb 27 21:26:29 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as /opt/oracle/product/10.2/db_1/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =121
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 1000
sessions = 1105
__shared_pool_size = 184549376
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
nls_language = ENGLISH
nls_territory = UNITED KINGDOM
filesystemio_options = SETALL
sga_target = 1577058304
control_files = /opt/oracle/oradata/rep/control.001.dbf, /opt/oracle/oradata/rep/control.002.dbf, /opt/oracle/oradata/rep/control.003.dbf
db_block_size = 8192
__db_cache_size = 1342177280
compatible = 10.2.0
Fri Feb 27 21:26:31 2009
ALTER DATABASE MOUNT
Fri Feb 27 21:26:35 2009
Setting recovery target incarnation to 1
Fri Feb 27 21:26:36 2009
Successful mount of redo thread 1, with mount id 740543687
Fri Feb 27 21:26:36 2009
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Fri Feb 27 21:26:36 2009
ALTER DATABASE OPEN
Fri Feb 27 21:26:36 2009
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Fri Feb 27 21:26:37 2009
Started redo scan
Fri Feb 27 21:26:41 2009
Completed redo scan
481654 redo blocks read, 13176 data blocks need recovery
Fri Feb 27 21:26:50 2009
Started redo application at
Thread 1: logseq 25176, block 781367
Fri Feb 27 21:26:50 2009
Recovery of Online Redo Log: Thread 1 Group 6 Seq 25176 Reading mem 0
Mem# 0: /opt/oracle/oradata/rep/redo_a/redo06.log
Mem# 1: /opt/oracle/oradata/rep/redo_b/redo06.log
Fri Feb 27 21:26:53 2009
Completed redo application
Fri Feb 27 21:27:00 2009
Completed crash recovery at
Thread 1: logseq 25176, block 1263021, scn 77945260488
13176 data blocks read, 13176 data blocks written, 481654 redo blocks read
Fri Feb 27 21:27:02 2009
Expanded controlfile section 9 from 1168 to 2336 records
Requested to grow by 1168 records; added 4 blocks of records
Thread 1 advanced to log sequence 25177
Thread 1 opened at log sequence 25177
Current log# 7 seq# 25177 mem# 0: /opt/oracle/oradata/rep/redo_a/redo07.log
Current log# 7 seq# 25177 mem# 1: /opt/oracle/oradata/rep/redo_b/redo07.log
Successful open of redo thread 1
Fri Feb 27 21:27:02 2009
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Feb 27 21:27:02 2009
SMON: enabling cache recovery
Fri Feb 27 21:27:04 2009
Successfully onlined Undo Tablespace 1.
Fri Feb 27 21:27:04 2009
SMON: enabling tx recovery
Fri Feb 27 21:27:04 2009
Database Characterset is AL32UTF8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=17, OS id=4563
Fri Feb 27 21:27:08 2009
Completed: ALTER DATABASE OPEN
Fri Feb 27 22:46:04 2009
Thread 1 advanced to log sequence 25178
Current log# 8 seq# 25178 mem# 0: /opt/oracle/oradata/rep/redo_a/redo08.log
Current log# 8 seq# 25178 mem# 1: /opt/oracle/oradata/rep/redo_b/redo08.log
Fri Feb 27 23:43:49 2009
Thread 1 advanced to log sequence 25179
Current log# 9 seq# 25179 mem# 0: /opt/oracle/oradata/rep/redo_a/redo09.log
Current log# 9 seq# 25179 mem# 1: /opt/oracle/oradata/rep/redo_b/redo09.log
Fri Mar 13 20:09:29 2009
MMNL absent for 1194469 secs; Foregrounds taking over
Fri Mar 13 20:10:16 2009
Thread 1 advanced to log sequence 25180
Current log# 10 seq# 25180 mem# 0: /opt/oracle/oradata/rep/redo_a/redo10.log
Current log# 10 seq# 25180 mem# 1: /opt/oracle/oradata/rep/redo_b/redo10.log
Fri Mar 13 20:21:17 2009
Thread 1 advanced to log sequence 25181
Current log# 1 seq# 25181 mem# 0: /opt/oracle/oradata/rep/redo_a/redo01.log
Current log# 1 seq# 25181 mem# 1: /opt/oracle/oradata/rep/redo_b/redo01.log

yes, you are right. I just found that the server was shutdown for more than 4 hours and server came back online @ 8:08pm and I think within few minutes those old timestamp appeared in the alertlog. We have a table which captures current timestamp from the db and timestamp from application and usually both columns are same. But following are the rows inserted during the time of the issue. Not sure why this has happened. One more thing is that the listener was started and on while database was starting and performing instance recovery.
DBTimestamp_ ApplicationTimestamp_
27-02-2009 21:27:45 13-03-2009 20:08:42
27-02-2009 21:31:47 13-03-2009 20:08:43
27-02-2009 21:31:54 13-03-2009 20:08:43
27-02-2009 21:33:39 13-03-2009 20:08:42
27-02-2009 21:35:47 13-03-2009 20:08:42
27-02-2009 21:37:45 13-03-2009 20:08:42
27-02-2009 21:38:24 13-03-2009 20:08:42
27-02-2009 21:39:42 13-03-2009 20:08:42
27-02-2009 21:40:01 13-03-2009 20:08:42
27-02-2009 21:41:13 13-03-2009 20:08:42
27-02-2009 21:44:07 13-03-2009 20:08:43
27-02-2009 21:53:54 13-03-2009 20:08:42
27-02-2009 22:03:45 13-03-2009 20:08:42
27-02-2009 22:07:02 13-03-2009 20:08:42

ORA-01403: no data found in alert.log

Dear All,
I am getting ORA-01403: no data found in alert.log.Could you pls help me out what could be reasons behind it..Due to this i m getting loads of alerts.Pls suggest.
Thanks

ORA-01403 No Data Found
Typically, an ORA-01403 error occurs when an apply process tries to update an existing row and the OLD_VALUES in the row LCR do not match the current values at the destination database.
Typically, one of the following conditions causes this error:
Supplemental logging is not specified for columns that require supplemental logging at the source database. In this case, LCRs from the source database might not contain values for key columns. You can use a DML handler to modify the LCR so that it contains the necessary supplemental data. See "Using a DML Handler to Correct Error Transactions". Also, specify the necessary supplemental logging at the source database to prevent future errors.
There is a problem with the primary key in the table for which an LCR is applying a change. In this case, make sure the primary key is enabled by querying the DBA_CONSTRAINTS data dictionary view. If no primary key exists for the table, or if the target table has a different primary key than the source table, then specify substitute key columns using the SET_KEY_COLUMNS procedure in the DBMS_APPLY_ADM package. You also might encounter error ORA-23416 if a table being applied does not have a primary key. After you make these changes, you can reexecute the error transaction.
The transaction being applied depends on another transaction which has not yet executed. For example, if a transaction tries to update an employee with an employee_id of 300, but the row for this employee has not yet been inserted into the employees table, then the update fails. In this case, execute the transaction on which the error transaction depends. Then, reexecute the error transaction.
There is a data mismatch between a row LCR and the table for which the LCR is applying a change. Make sure row data in the table at the destination database matches the row data in the LCR. When you are checking for differences in the data, if there are any DATE columns in the shared table, then make sure your query shows the hours, minutes, and seconds. If there is a mismatch, then you can use a DML handler to modify an LCR so that it matches the table. See "Using a DML Handler to Correct Error Transactions".
Alternatively, you can update the current values in the row so that the row LCR can be applied successfully. If changes to the row are captured by a capture process at the destination database, then you probably do not want to replicate this manual change to destination databases. In this case, complete the following steps:
Set a tag in the session that corrects the row. Make sure you set the tag to a value that prevents the manual change from being replicated. For example, the tag can prevent the change from being captured by a capture process.
EXEC DBMS_STREAMS.SET_TAG(tag => HEXTORAW('17'));
In some environments, you might need to set the tag to a different value.
Update the row in the table so that the data matches the old values in the LCR.
Reexecute the error or reexecute all errors. To reexecute an error, run the EXECUTE_ERROR procedure in the DBMS_APPLY_ADM package, and specify the transaction identifier for the transaction that caused the error. For example:
EXEC DBMS_APPLY_ADM.EXECUTE_ERROR(local_transaction_id => '5.4.312');
Or, execute all errors for the apply process by running the EXECUTE_ALL_ERRORS procedure:
EXEC DBMS_APPLY_ADM.EXECUTE_ALL_ERRORS(apply_name => 'APPLY');
If you are going to make other changes in the current session that you want to replicate destination databases, then reset the tag for the session to an appropriate value, as in the following example:
EXEC DBMS_STREAMS.SET_TAG(tag => NULL);
In some environments, you might need to set the tag to a value other than NULL.

Errors in archiving in alert log

Hi
I have a Oracle 9i database (9.2.0.7) for which I turned on arhivelog mode a week ago. In this db, inthe alert log there are following errors:
ARC1: Evaluating archive log 1 thread 1 sequence 1221
ARC1: Unable to archive log 1 thread 1 sequence 1221
Log actively being archived by another process
ARC1: Evaluating archive log 2 thread 1 sequence 1222
ARC1: Unable to archive log 2 thread 1 sequence 1222
Log actively being archived by another process
and there are no message like 'Completed archiving' because of another issue - there was an error in specifying the log format. The value of log_archive_format was incorrectly set to "DB001_%s_%t_%r.arc" so there is also another trace file which says that:
*** SESSION ID:(9.1) 2009-03-11 08:42:00.023
ORA-00294: invalid archivelog format specifier 'r'
So there are two things: 1) To change the archive log format
2) To deal with the other issue: Unable to archive log 2 thread 1 sequence 1222
Log actively being archived by another process
What is the process to do this? Will be thankful for help. The database is up now.
Thanks
Nirav
Edited by: orausern on May 1, 2009 1:14 AM

orausern wrote:
Thank you for the suggestion, I tried it but it is giving an error like:
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified
also the parameter log_archive_format is not system or session modifiable. My concern is that since this error is more than one week old, will it allow me to shut down the db cleanly (when I get the permission to do so) or will there be some issue if i try to shut the db and then restart. so I am not sure how to proceed..
Thanks
NiravI guess you have taken it wrong, this parameter is indeed changeable but the effect of this would come in the next startup only a its a static parameter.
http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch195.htm#REFRN10089
So you need to do some thing like this,
alter system set log_archive_format=<your_desired_format> scope=spfile;Do a reboot and the parameter settings would come into effect. Any dba account should be able to change this parameter but for the bounce of the db, you need to have Sysdba privs. This parameter won't effect your startup or shutdown, they should proceed without issues.
HTH
Aman....

Multiple ORA-27300, ORA-27301 and ORA-27302 in alert log

Hello all,
Looking for some guidance with a 10.2.0.1 database on Windows 2003 Enterprise Edition server. I have an SR open with Oracle, but getting the usual run-around and no conclusive explanations.
A couple of weeks ago, the database started throwing the following in the alert log:
Errors in file d:\oracle\admin\hdprd\bdump\hdprd_cjq0_404.trc:
ORA-27300: OS system dependent operation:WaitForSingleObject failed with status: 0
ORA-27301: OS failure message: The operation completed successfully.
ORA-27302: failure occurred at: sssxcpttcs5
Checking the trace file shows:
*** 2011-03-22 17:37:21.391
*** SERVICE NAME:(SYS$BACKGROUND) 2011-03-22 17:36:53.890
*** SESSION ID:(327.1) 2011-03-22 17:36:53.890
Waited for process J000 to initialize for 60 seconds
*** 2011-03-22 17:37:21.391
Dumping diagnostic information for J000:
OS tid = 3620
Memory (Avail/Total): Ph:6548M/8190M, Ph+PgF:10684M/12074M, VA:994M/2047M
CPU Load: 5%
------------------- Call Stack Trace ---------------------
calling location entry point arg #1 arg #2 arg #3 arg #4
7C82847C 00000000 00000000 00000000 00000000 00000000
77E41A89 77E64849 00000000 00000000 00000000 00000000
_slxefo+154                                                      00000000                                                         00000000 00000000 00000000 00000000
slxcfot+805                                                     slxefo+0 00000000 00000000 00000000 00000000
lxlfopn+128                                                     slxcfot+0 412dd744 412dd98c 60b2c20c 60b2c208
lxldlod+56                                                      lxlfopn+0 60b382dc 412dd98c 00000000 00000000
_lxdlobj+79                                                      00000000                                                         60b382dc 412dd98c 0a4957f0 00000001
lxdgetobj+187                                                   lxdlobj+0 00000001 00000000 0a49df34 00000000
lxplset+49                                                      lxdgetobj+0 00000000 00000000 00000000 00000000
lxhLaToId+146                                                   lxplset+0 00000001 0a49dd14 0a49df34 00000000
lxhenvquery+197                                                 lxhLaToId+0 00000000 00000000 00000000 00000000
lxhLangEnv+352                                                  lxhenvquery+0 00000000 00000000 00000000 00000000
62747F74 62765084 0a49dd14 00000000 0a49df34 0a49df34
60987803 60A35104 00000000 00000000 00000000 00000000
60986EEE 60986EFC 3b512c78 412df6b4 412dfd84 00000100
6098798C 60986ED8 3b512c78 412df6b4 412dfd84 00000100
npinli+78                                                       nlstdgo+0 00000000 00000000 00000000 00000000
opiinit+142                                                     npinli+0 00000001 00000000 00000000 00000000
opimaireal+194 _opiinit+0                                                       00000000 00000000 00000000 00000000
opimai+92                                                       opimai_real+0 00000003 412dfeec 00000000 00000000
BackgroundThreadStart@4+422                                     opimai+0 00000000 00000000 00000000 00000000
77E6482C 00000000 00000000 00000000 00000000 00000000
---------------- End of Call Stack Trace -----------------
Call stack acquisition performance stats:
setup time (lock acquis., memory alloc.): 0 ms
frame get time (time the target proc was suspended): 0 ms
symbol translation time: 157 ms
total time: 157 ms
The database remains functional while this is happening, but we are no longer able to establish new sessions to the database. The only remedy so far, as is the case with most Windows issues, is to reboot the server. The support analyst has recommended that we add the "/3gb" switch to the boot.ini as he feels we are hitting the 2GB limitation for a single process. My concern is that in looking at the trace file, it would appear that there's only around 1.6GB of memory consumed in total on the server (8190M - 6548M = 1642M), so there should be no single process that's coming even close to the 2GB limitation. I've been watching the oracle.exe process for the last week, and it always hovers around 700M. The total SGA size is about 600M.
Interestingly enough, we're in the process of downgrading the database from Enterprise Edition to Standard edition and on the development server, we've currently got the old 10.2.0.1 EE database and the new 10.2.0.5 SE database running concurrently. The EE version has encountered the same issue described above, while the SE version has not.
My other problem is that I work in the pharmaceutical industry and this is a heavily regulated database and I cannot make arbitrary changes to databases/servers without evidence to support the change.
Any Oracle/Windows experts out there that can shed some light on this problem?
Thanks

Thanks to both of you for the speedy response. I have already seen that article, as well as 790397.1 - PROCESS J000 And M000 Die [ID 790397.1]. I'm just a little confused as to why Oracle is saying it's an out of memory condition when there's nothing in the log or trace files (other than the condition matches a couple of articles they have) that support the conclusion. Don't get me wrong, I'm certainly not an Oracle on Windows expert, most of my stuff revolves around Linux/UNIX and I avoid anything windows like the plague, other than starting a putty session.
My understanding is that each process in a windows 32bit environment gets a 4GB Virtual Address Space, which is split into a lower 2GB application space and an upper 2GB kernel space. If the trace file is showing that only 1.6GB of physical memory has been consumed, wouldn't this indicate that there isn't a single process on the server that is even close to reaching it's 2GB limitation?

Alert log is not updated in Oracle 8i

Database is running
Alert log is not updated,not even after manually logswitch
I have created job on this but , it is not running itself while same job is runnig on other Db
DBA_JOBS shows null value for this job
I can run job manually ..then DBA_JOBS shows value
After creating a job ... it shows in invalid objects list
Thanks in advance

Oracle_2410 wrote:
Please somebody help me !!!Its 3 month old problem!!!
For first problem "Alert log not getting updated"
Please post the os version and name. And output of below query
show parameter background
ls -lart (or dir) <path shown above>Regards
Anurag

Operations manager console shows old alerts

Hi All,
I Have this issue regularly, I am using SCOM 2007 R2 CU4. But recently this issue has become very frequent. I see more number of old alerts rather than new alerts in my SCOM console. Below is a screen shot. Is there any specific reason for this ? If
yes, How can i overcome this issue.
I checked the Health of the databases (Both Opsmanager & Ops manager warehouse database). Both are healthy they have 0 consistency errors in them. And have enough free space in them.
Below is the SQL Query what is used to check them.
For OpsmanagerDB -
DBCC CHECKDB ('Operationsmanager')
For Ops manager Data warehouse:
DBCC CHECKDB ('OperationsmanagerDW')
Ops db has 16GB Free from total of 40GB.
Warehouse DB: 56GB Free from total size of 180GB.
Gautam.75801

Hi There,
My services are Running and up. Post analysing the event logs i found that the below event is frequent on my RMS Pointing towards few of my agents and The events are also on the name of my RMS
20022
The description for Event ID 20022 from source OpsMgr Connector cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
{E6B56BC0-A270-9E8D-2738-B7238757EB67}
My SCOM Agent name
MY Management group name
{95515F4D-7E15-9FAB-5D07-E434220E5F57}
The handle is invalid
==========================
Also lot of 2115 Event logs
=======================
Also lots and lots of 29103 & 29102 Information events
The description for Event ID 29103 from source OpsMgr Config Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
My SCOM Agent name
57 35 29 C1 F3 42 12 96 AF BA 4C 84 01 4D 49 2D E2 C5 60 D2
{7a7af7a4-602c-ad7d-7d36-949bd187500a}
The handle is invalid
===================================
Event id 8000 on RMS Name its self
The description for Event ID 8000 from source HealthService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
CINSCOM
Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData
MY RMS FQDN
{6C3444C3-3990-BB5A-F25E-289D8F427570}
34
The handle is invalid
======================================
Event id 31551
The description for Event ID 31551 from source Health Service Modules cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
My management group name
Microsoft.SystemCenter.DataWarehouse.CollectEntityHealthStateChange
MY RMS FQDN
{6C3444C3-3990-BB5A-F25E-289D8F427570}
InvalidOperationException
Cannot access destination table 'State.StateStage'.
The handle is invalid
======================================
Event id 5304
The description for Event ID 5304 from source HealthService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
95515f4d-7e15-9fab-5d07-e434220e5f57
My management group name
The handle is invalid
====================================================
Event id 5302
The description for Event ID 5302 from source HealthService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
95515f4d-7e15-9fab-5d07-e434220e5f57
My management group name
The handle is invalid
====================================
Event id 5500
The description for Event ID 5500 from source HealthService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
{95515F4D-7E15-9FAB-5D07-E434220E5F57}
72E278FE-075C-BB33-1FF4-1F5F22988F8D
5F1924C9-F4B2-BAA6-7D50-FFDC523D99BB
2014-11-21T07:57:33.0664640-05:00
2014-11-21T10:36:34.1361505-05:00
Success
Success
My SCOM Management group
My scom Agent name
The handle is invalid
===========================================================
Strange thing is that all the Above events different but the descriptions are pointing towards healthservie. Does any one have any idea what is going on in the RMS?
Gautam.75801

How to check particular error in alert log file

Hi all,
How to check particular error in alert log file,for supose if i get error in batabase yesterday 4 pm & today i want to check alert log file to get basic idea..it might be a big file so how to check that particular error..
Thanks & regards,
Eswar..

What's your oracle version?
If you are in 11g you can use adrci tool
1- set homes diag/rdbms/orawiss/ORAWISS/ : the rdbms home
2- show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term : to find all the ORA-% errors in the alert file
3- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term : to find all the ORA-% errors in the alert file during the last 51 days,
4- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-1/24 " -term : to find all the ORA-% errors in the alert file during the last hour,
5- show alert -P "MESSAGE_TEXT LIKE '%ORA-12012%' and originating_timestamp > systimestamp-1/24 " -term : to find the particular ORA-12012 error in the alert file during the last hour,
Example:
[oracle@wissem wissem]$ adrci
ADRCI: Release 11.2.0.1.0 - Production on Wed May 4 10:24:54 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ADR base = "/home/oracle/app/oracle"
adrci> set homes diag/rdbms/orawiss/ORAWISS/
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-'" -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
2010-12-11 19:45:41.289000 +01:00
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/home/oracle/app/oracle/oradata/ORAWISS/system01.dbf'
ORA-1547 signalled during: ALTER DATABASE RECOVER database until time '2011-01-21:10:48:00' ...
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
ORA-12012: error on auto execute of job 29
ORA-01435: user does not exist
2011-03-15 11:39:37.571000 +01:00
opiodr aborting process unknown ospid (31042) as a result of ORA-609
2011-03-15 12:04:15.111000 +01:00
opiodr aborting process unknown ospid (3509) as a result of ORA-609
adrci>
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
2011-03-15 10:19:45.316000 +01:00
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j006_5536.trc:
ORA-12012: error on auto execute of job 26
ORA-01435: user does not exist
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
ORA-12012: error on auto execute of job 29
ORA-01435: user does not exist
2011-03-15 11:39:37.571000 +01:00
opiodr aborting process unknown ospid (31042) as a result of ORA-609
2011-03-15 12:04:15.111000 +01:00
opiodr aborting process unknown ospid (3509) as a result of ORA-609
adrci>

How to view alert log?

I tried clicking on the xml alert log, but it goes into IE and tells me "Cannot view xml input using xsl style sheet...Only one top level element allowed in an xml document". I don't see any adrci, and I can't find any text file alert log? trace directory only has files beginning with cdump. database and dbs directories don't have it. And nothing about it in the docs?
I hope I'm missing something obvious. The database is running. XP Pro SP3.

Udo wrote:
Hello Joel,
the good old text alert log is still there, it just moved a bit. The default location would be ORACLE_HOME\diag\rdbms\xe\xe\trace, e.g. D:\oracle\product\database_xe_11_2\app\oracle\diag\rdbms\xe\xe\trace for the instance on my machine.Yep, that's the trace directory I was looking in, it only has an xml.
See this thread for further hints: {thread:id=2281565}(You had an extra ampersand in the thread id). Yeah, 'Diag Trace' says same directory.
Anyone know how to get the css right? I'm clueless about such things.
>
-Udo

ST04 alert log

Dear Techies
I am running SAP 4.6 B with oracle 10g on solaries
Recently i have upgraded the database from 9.2 to 10g since then iam unable to view Alert log from ST04.
I am getting ORA-1722 error with ABAP dump DBIF_DSQL2_SQL_ERROR
Thanks
Haroon

Hi,
Unfortunately, there is no workaround. 10g changes a lot of things (for example more columns in v$session) and ST04.
Some things were corrected for old versions but not everything.
As I mentioned before, 10g was not supported for releases < 4.6C. From application point of view thre will not be problems, but monitoring tools are expected to have "issues". I have only seen 10g in low versions as a middle step for an upgrade.

Old alert logs

Similar Messages

Maybe you are looking for