Physical standby failed to start MRP process

Hi,
I have a qa db which is in ASM. I have a qa standby which is a physical standby also in ASM. I added space to the primary. Unfortunately, the standby diskgroup did not have enough space and standby mrp process crashed. I edited the primary data files to release some space and tried to restart the standby but it does not seem to work.
What next?

Er, Can you provide more information?
Like maybe some details from the alert logs?
Or maybe even the error message you get when you try to restart the standby
The more information the easier it is to debug at a distance.
jason.
http://jarneil.wordpress.com

Similar Messages

Rman backup on physical standby database without cancelling MRP

Hi all,
Could anyone share, is this possible to take RMAN backup on physical standby database without cancelling MRP process.
regarrds,

Hi,
On Standby Side:
SQL> alter database mount;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        405
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        404
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:31:43 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=390 RECID=391 STAMP=815416638
input archived log thread=1 sequence=391 RECID=392 STAMP=815421952
input archived log thread=1 sequence=392 RECID=393 STAMP=815422343
input archived log thread=1 sequence=393 RECID=394 STAMP=815422434
input archived log thread=1 sequence=394 RECID=395 STAMP=815422570
input archived log thread=1 sequence=395 RECID=396 STAMP=815476598
input archived log thread=1 sequence=396 RECID=397 STAMP=815476615
input archived log thread=1 sequence=397 RECID=398 STAMP=815476645
input archived log thread=1 sequence=398 RECID=399 STAMP=815477471
input archived log thread=1 sequence=399 RECID=400 STAMP=815477475
input archived log thread=1 sequence=400 RECID=401 STAMP=815477628
input archived log thread=1 sequence=401 RECID=403 STAMP=815584146
input archived log thread=1 sequence=402 RECID=402 STAMP=815584137
input archived log thread=1 sequence=403 RECID=405 STAMP=816017446
*input archived log thread=1 sequence=404 RECID=404 STAMP=816017444*
*input archived log thread=1 sequence=405 RECID=406 STAMP=816017455*
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T153202_8spm937d_.bkp tag=TAG20130521T153202 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_390_8s48hfrp_.arc RECID=391 STAMP=815416638
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_391_8s4fohwb_.arc RECID=392 STAMP=815421952
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_392_8s4g1q0v_.arc RECID=393 STAMP=815422343
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_393_8s4g4l8z_.arc RECID=394 STAMP=815422434
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_394_8s4g8t9h_.arc RECID=395 STAMP=815422570
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_395_8s631622_.arc RECID=396 STAMP=815476598
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_396_8s631qjj_.arc RECID=397 STAMP=815476615
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_397_8s632od8_.arc RECID=398 STAMP=815476645
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_398_8s63whqc_.arc RECID=399 STAMP=815477471
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_399_8s63wly4_.arc RECID=400 STAMP=815477475
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_400_8s641d8j_.arc RECID=401 STAMP=815477628
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_401_8s9d21jk_.arc RECID=403 STAMP=815584146
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_402_8s9d1skv_.arc RECID=402 STAMP=815584137
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_403_8spm6p4h_.arc RECID=405 STAMP=816017446
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_404_8spm6mqj_.arc RECID=404 STAMP=816017444
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc thread=1 sequence=405
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T153213_8spm9fnc_.bkp tag=TAG20130521T153213 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:02:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T153213_8spmfqxf_.bkp tag=TAG20130521T153213 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> exit
Recovery Manager complete.
[oracle@oel62-x64 Desktop]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue May 21 15:34:42 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        405
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        404
SQL> There have no problem, backup database when MRP is running. But if you want delete, then you are getting RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
And will not delete this archived log, because it is needed for standby or upstream capture process.
Updated
When MRP stoped
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:46:07 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=24 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=405 RECID=406 STAMP=816017455
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154617_8spn3s9w_.bkp tag=TAG20130521T154617 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc RECID=406 STAMP=816017455
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154618_8spn3v4f_.bkp tag=TAG20130521T154618 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154618_8spn6779_.bkp tag=TAG20130521T154618 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> Apply process is stopped and new redo received from primary.
SQL> select max(Sequence#) from v$archived_log;
MAX(SEQUENCE#)
        407
SQL> select max(Sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
        405
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 Desktop]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:49:28 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup database plus archivelog delete all input;
Starting backup at 21-MAY-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=32 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=406 RECID=407 STAMP=816018527
input archived log thread=1 sequence=407 RECID=408 STAMP=816018530
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154937_8spnb1y3_.bkp tag=TAG20130521T154937 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: deleting archived log(s)
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_406_8spn8hkn_.arc thread=1 sequence=406
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_407_8spn8l69_.arc thread=1 sequence=407
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154939_8spnb3f5_.bkp tag=TAG20130521T154939 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 21-MAY-13
channel ORA_DISK_1: finished piece 1 at 21-MAY-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154939_8spndhly_.bkp tag=TAG20130521T154939 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-MAY-13
Starting backup at 21-MAY-13
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 21-MAY-13
RMAN> I think, codes is understandable.
Regard
Mahir M. Quluzade
Edited by: Mahir M. Quluzade on May 21, 2013 3:36 PM

Dreaded "Operations Manager failed to start a process" error (2012 R2)

I know this error has been covered many times, and on many topics, but this time mine is slightly different.   It's
NOT the
"SCOMpercentageCPUTimeCounter" error covered by Kevin Holman.
Also, I am running SCOM 2012 R2 UR4 (7.1.10226.1046) and everything seems correctly patched (MS and agents), like
suggested by Nicole Welch and Kevin Holman as well.
So my environment is a fresh installation of SCOM 2012 R2, and I am transferring to this new Management Group, the monitored servers from our old SCOM 2012 "R1" (which I did not upgrade but rather made a brand new independent install). So
all servers aren't migrated yet, but I would like to solve this error before. This error did NOT happen in "R1", nor was it overridden (I imported the exact same Management Packs anyway).
On 2012 R2, it happens on almost all new monitored machines, mainly Read-Only Domain Controllers (RODCs).
Here is the kind of alert text I am getting:
Het om 10:10:15 gestarte proces is beëindigd als gevolg van een uitvoerverzamelfout als gevolg van fout 0x80070057 :
The parameter is incorrect.
; mogelijk zijn er gegevens verloren gegaan.
Opdracht die is uitgevoerd: "C:\Windows\system32\cscript.exe" //nologo "C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 193\24788\AD_Global_Catalog_Search_Response.vbs"
RODC02.mydomain.be (objectCategory=DMD) false 4 {9E253FCB-8AAF-491F-CCA3-E632C6C2800C}
Werkmap: C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 193\24788\
Dit is van invloed op een of meer werkstromen.
Werkstroomnaam: Microsoft.Windows.Server.2008.AD.DomainController.GCSearchTime.Monitor
Exemplaarnaam: RODC02
Our servers have Belgian (Dutch) regional settings, hence the language. But check out the highlighted info in bold.
The related event Number (in Alert Context) is 21404. Most other articles about this, mention 21402 or 21403. I suppose they all must be related but still, it's a new one here.
There you have the failing VBS file. I checked all alerts and there seem to be different files concerned overall. Other examples:
C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 233\22737\AD_Database_and_Log.vbs    (from almost all RODCs)
C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 196\19876\Microsoft.Windows.Server.Legacy.FreeSpace.vbs
(also from an RODC)
C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 5891\338282\Microsoft.Windows.Server.CPUUtilization.Monitortype.vbs 95 15
SCOM02.mydomain.be 1.4119384288787842     (this one is from my second Management Server..)
Repeat count of the alert is 1 to 2 a day, so it's not nightmareish, but still, requires to be fixed. I suspect that even if there is a different VBS file concerned, since the eventID and the alert text are the same, the repeat count will just increase,
not showing the last actual VBS concerned.
I connect to each of these servers, and browse to the directory containing the file, and the folder is there, the file is there. The error text mentions incorrect parameters but they still seem OK to me.
I found something which might be worth noting: when browsing to the directory, be it on an RODC or on the SCOM server, I get a permission popup requiring some admin rights to do so - although I am using my domain admin (+SCOM+SQL+local
admin everywhere) account:
SCOM services use the Local System account to run, on every machine. I thought Local System shouldn't be concerned with these permissions popups, but normally the domain/local admins aren't either, yet I am.
The "Health service" folder is the only one from the "C:\Program Files\Microsoft Monitoring Agent\Agent" folder to be concerned with this; I can browse without trouble to any other directory there.
After a SCOM service stop, I renamed the "Health Service state" folder (as you can see on the screenshot, there is a "Health Service State bak" folder) and let the service recreate it after a restart, to ensure it was clean and with
appropriate permissions , but it doesn't help.
Might that be a clue?
Or else what? I'm getting confused and don't find a suitable solution.
dd
Bix

On Thu, 4 Dec 2014 14:20:22 +0000, Bixessss wrote:
I know this error has been covered many times, and on many topics, but this time mine is slightly different.   It's*NOT* the "SCOMpercentageCPUTimeCounter" error covered by Kevin Holman <http://blogs.technet.com/b/kevinholman/archive/2010/02/23/a-new-script-error-scompercentagecputimecounter-vbs-invalid-class.aspx>.
Also, I am running *SCOM 2012 R2 UR4* (7.1.10226.1046) and everything seems correctly patched (MS and agents), likesuggested by Nicole Welch <http://nicolewelchscom.wordpress.com/2013/10/01/operations-manager-failed-to-start-a-process/>
and Kevin Holman as well.
This forum is for security issues related to Windows Server and not for
System Center questions.
Post your question in one of the following forums:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=systemcenteroperationsmanager
Thanks.
Paul Adare - FIM CM MVP
Never trust a computer you can't lift. - Stan Masor

Failed to start essbase process: number of back up files exceeds limit

Can someone help to take a look at this?
More details is logged in bug 11887650
Failed to start essbase process, message in log file:
11/03/18 11:44:10 Start process
Info: Essbase is reducing the number of soft file descriptors because the 32K limit has been exceeded. Exceeding the limit may significantly increase application load time.
Environment variable [HYPERION_LOGHOME] is set - use it to define Log location folder.
Log location is [u01/APPLTOP/instance/BIInstance/diagnostics/logs/Essbase/essbaseserver3/essbase].
ODL log location is [u01/APPLTOP/instance/BIInstance/diagnostics/logs/Essbase/essbaseserver3/agent-log].
[Fri Mar 18 11:44:10 2011]Local/ESSBASE0///4072736080/Warning(1056807)
The number of back up files found on disk (40) exceeds the configured limit which is 2
[Fri Mar 18 11:44:10 2011]Local/ESSBASE0///4072736080/Info(1051283)
Retrieving License Information Please Wait...
[Fri Mar 18 11:44:10 2011]Local/ESSBASE0///4072736080/Info(1051286)
License information retrieved.
65535 Essbase user 65535 Planning user system
Logging configuration class "oracle.core.ojdl.logging.LoggingConfiguration" failed
oracle.core.ojdl.logging.LoggingConfigurationException: ODL-52050: unable to process file '/u01/APPLTOP/instance/BIInstance/Essbase/essbaseserver3/bin/logging.xml', XML parse exception (line: 5, column: 38): org.xml.sax.SAXParseException: Attribute "class" is required and must be specified for element type "log_handler".
Mar 18, 2011 11:44:14 AM oracle.security.jps.az.internal.common.scanner.PolicyChangeScannerThread run
INFO: Policy store cleanup thread started.
Mar 18, 2011 11:44:14 AM
INFO: EPMCSS-CSS Fusion system initialized successfully. : [2724 ms]
[Fri Mar 18 11:44:14 2011]Local/ESSBASE0///4072736080/Info(1051199)
Single Sign-On Initialization Succeeded !
[Fri Mar 18 11:44:14 2011]Local/ESSBASE0///4072736080/Info(1051639)
Info: Essbase is reducing the number of soft file descriptors because the 32K limit has been exceeded. Exceeding the limit may significantly increase application load time.
Essbase 64-bit - Release 11.1.2 (ESB11.1.2.1.0B154)

I am an infrastructure idiot (I have all kinds of other idiocy available as well -- I am versatile), but I found:
http://troubleshooot.wordpress.com/2010/05/26/essbase-login-is-not-working/
To my ignorant eyes, this looks like some kind of *nix-centric issue.
If the post doesn't help, perhaps one of the infrastructure guys will chime in.
Regards,
Cameron Lackpour

SCOM 2012 Operations Manager Failed to start a process

We have recently upgraded from SCOM 2007 to SCOM 2012. We are not getting a great deal of “Operations Manager Failed to start a process”. The process varies including:
DiscoverSQL2008ASDiscovery.vbs
DiscoverSQL2008DBEngineDiscovery.vbs
DiscoverSQL2008ASDiscovery.vbs
Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs
I have researched and researched. I know that you can try to run the scripts locally on the machine but it seems the scripts never make it to the machine. I go to the path in the error, no luck. I look in the other folders as I know that SCOM moves the scripts,
and I even search the entire C drive but the scripts are not getting to the server. The folder is not even making it. For example:
Command executed: "C:\Windows\system32\cscript.exe" /nologo "Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs" SERVER true Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring
Host Temporary Files 11606\1759\
The script is not there and the folder \1759 is not there either.
I have removed and reinstalled the client.
Antivirus is fine, up to date and not blocking on any of the machines.
I have stopped the “System Center Management service” and renamed the “Health Service State” folder and it recreates fine but not long after I get the warning in SCOM about “Operations Manager Failed to start a process”.
I look in event viewer for Operations Manager on this particular one and I see a lot of:
Performance data from the Health Service could not be collected since required registry keys could not be read, the error was 2L (The system cannot find the file specified.). Event ID 6001.
I tried the fix of
"lodctr MOMConnectorCounters.ini" and "lodctr HealthServiceCounters.ini" but I get “error
encountered while updating text in registry. Status: 0”. Again I am using SCOM 2012.
Do I need to look at each failed script or is there a overall issue because the scripts are not making it to the machines. Any ideas?

I guess you might need to run "mofcomp sqlmgmproviderxpsp2up.mof".
Thanks, S K Agrawal

Switchover to physical standby failed

Hi gurus,
Could anyone pls help for this issue, i'm working on oracle 9i dataguard in solaris box. we succesully switchover our physical standby to primary but when tried to bring back again to physical standby it is throwing an error
SQL> alter database commit to switchover to physical standby;
alter database commit to switchover to physical standby
ERROR at line 1:
ORA-16014: log 1 sequence# 91775 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/oracle/u07/oradata/odb/redo_1a.log'
ORA-00312: online log 1 thread 1: '/oracle/u08/oradata/odb/redo_1b.log'
ORA-00312: online log 1 thread 1: '/oracle/u09/oradata/odb/redo_1c.log'
Please advice
regards,
shaan

Hi,
There is already a thread which you opened Up you can reply back in that..
switchover to physical standby failed
- Pavan Kumar N

Failed to start worker process: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569

We just rebuilt our machine with server 2012, and it was working flawlessly and then randomly it started giving me this error if i would try to start up a machine. At first this was just an annoyance but now it is worrying me greatly. I have tried
everything from logging on as the domain admin account to the actual server administrator account. Nothing seems to start these machines up, and I need them to start.
'Computer1' failed to start worker process: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

Hi,
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as 'Answered' as the previous steps should be helpful for many similar scenarios.
If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
In addition, we'd love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
Thanks!
Lawrence
TechNet Community Support

Error in starting MRP process in Standby database.

Hi All,
OS:Windows server 03
DB:11g
I am creating a Standby database, everything is fine until i fire the below command to start the MRP process to start the recovery of the database.
alter database recover managed standby database disconnect from session;MRP0 started with pid=27, OS id=6640
2013-02-07 17:59:48.515000 +05:30
started logmerger process
Managed Standby Recovery not using Real Time Apply
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSAUX01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\APP\ORACLE\ORADATA\TEST\TEST\UNDOTBS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\APP\ORACLE\ORADATA\TEST\TEST\USERS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
MRP0: Background Media Recovery terminated with error 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_pr00_7984.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Recovery Slave PR00 previously exited with exception 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_mrp0_6640.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Completed: alter database recover managed standby database disconnect from session
Can anyone tell me why is this comming?
Regards,
Sphinx

Hi ,
Yes, it is on the same server.
I have used the below mentioned parameters to rename the files
At Primary Pfile:
*.db_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\datafiles\')
*.log_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\redologs\')
At Standby:
*.db_file_name_convert=('D:\app\oracle\testdr\oradata\datafiles\','D:\app\oracle\oradata\test\test\')
*.log_file_name_convert=('D:\app\oracle\testdr\oradata\redologs\','D:\app\oracle\oradata\test\test\')
But the output of v$datafile at standby is showing the path of Primary datafiles
I manually tried recovering them but it is prompting me the same error.
Regards
Edited by: $phinx19 on Feb 7, 2013 6:23 AM

Create physical standby failed at destination preparation step

I have tried several times to create a physical standby using Grid Control. Everytime, the job failed at the step "Destination Preparation". The log file indicated the following error message:
PLS-00553: character set name is not recognized.
This is because an extra word "PuTTY" was inserted into the spfile as shown in the following spfile, therefore, the instance cannot be started. In addition, everytime when issuing the command "cat spfilermslag.ora", the word "PuTTY" will automatically appear in the command line after the "cat spfilermslag.ora" command.
$ cat spfilermslag.ora
gé ú&PuTTYrmslag.__db_cache_size=150994944
rmslag.__large_pool_size=4194304
rmslag.__shared_pool_size=71303168
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/u01/app/oracle/admin/rmslag/udump'
[oracle@wppnode2 dbs]$ PuTTY
What is going on here? How can I fix the problem?
Thanks!

You can still carefully use the corrupted spfile to create a pfile and start your database with teh pfile, then create spfile from the pfile.
Make a copy of the spfilermslag.ora sand save it as initrmslag.ora. Open the spfile with notepad, carefully remove all the wrong characters at the begining and end of the file. Use the init file to startup the database
SQL>connect sys as sysdba
SQL>startup spfile=$ORACLE_HOME/dbs/initrmslag.ora
SQL>create spfile from pfile;
SQL>shutdown immediate
SQL>startup

Physical standby crash leads to peculiar process behavior on primary nodes

Hey all, we had an issue early this morning with our physical standby database in our production environment. It's an odd problem and I thought I'd share it to see if anyone else has come across a similar problem.
Our environment consists of a two node RAC cluster running 10.2.0.2 Enterprise on Red-Hat x86-64 Linux boxes. We have implemented a single physical standby at a remote site using real-time log apply.
Upon arrival this morning I discovered that a large portion of the primary database activity was a wait class event(ARCH wait on SENDREQ). The problem was quickly identified as a network issue between our site and the remote standby. However, the physical standby seemed to be running normal, with no messages in the alert logs regarding network disconnects. Further investigation showed that our log-apply had stopped all together early that morning. It seems the DBWR process crashed around 630am, as per this trace dump:
*** 2008-02-27 06:24:53.667
Waited for detached process: DBW0 for 300 seconds:
*** 2008-02-27 06:24:53.667
Dumping diagnostic information for DBW0:
OS pid = 10587
loadavg : 12.11 11.67 8.95
memory info: free memory = 0.00M
swap info: free = 0.00M alloc = 0.00M total = 0.00M
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
0 S oracle 2448 31813 0 78 0 - 13190 wait 06:07 ? 00:00:00 /bin/sh -c /usr/bin/gdb -quiet -x
/tmp/stacknvvano
/proc/10587/exe 10587 < /dev/null 2>&1
0 S oracle 2449 2448 0 78 0 - 38780 wait 06:07 ? 00:00:00 /usr/bin/gdb -quiet -x
/tmp/stacknvvano /proc/10587
/exe 10587
0 D oracle 10587 1 0 76 0 - 43072 - Jan04 ? 00:04:09 ora_dbw0_schclsdb
So what we did was restart the standby server and the database came up fine. We reinitiated log apply services and both databases did sync up. However
we are still seeing the "ARCH wait on SENDREQ" wait event from ARC0 and ARC1 on both the RAC instances.
We tried reseting the connection to the standby database, however did this not clear up the wait event. The system itself, as far as I can tell is not suffering, and redo logs are going across to the standby database without issue. What could be the problem with the ARC0 and ARC1 processes?
It would probably be helpful to mention that we don't actually use the ARCH processes for the log apply unless the standby falls behind. Archiving is handled by the local LNS process and remote RFS service. A quick instance restart would fix it, to be sure, but since this is happening in a production deployment in a 24x7 environment, I'd rather not have any downtime. A service request is of course filed, but since they have not gotten back to me yet and Metalink hasn't been of much help, I thought I'd see if any of you have seen this before. This giant gray blob on my grid control histogram is quite obnoxious. =) Thanks for taking the time to read. Cheers.
-Jim Henaghan

Just as an update to anyone else who may have this problem, we haven't found a good way to clear up our Archiver issue, so a instance restart will take place. Further research indicates the issue came about from a MRP process crash due to a known bug fixed in 10.2.0.4 (https://metalink.oracle.com/metalink/plsql/f?p=130:14:316259464254960300::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,5894403.8,1,0,1,helvetica)

Ora-38500 physical standby database not started

hiiii,
When i executed the command at physical standby database server.
it give error:
To start real-time apply:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> USING CURRENT LOGFILE;
Error at line 1:
ORA: 38500 using current logfile option not available without stand.
please help me how could i start physical standby database
Regards
Vaibhav Dixit

Hi Vaibhav,
What exactly do you want to do?
Alter database recover managed standby database; --->it will be in Manged Recovery mode.
Alter database mount standby database; ----> it will be mounted, but no log files applies.
Alter database open read only; ----> it will be open with read only option, but archeive logs will NOT be applied
If you want to apply the Archive logs which are trasfered from Primary, then you need to fire the below commands
Alter database recover managed standby database;
Alter database recover managed standby database using current logfile;
Alter database recover managed standby database using current logfile disconnect from session;
To stop applying archives then,
Alter database recover managed standby database cancel;
Thanks and Regards.
tnaresh1982

Operations Manager failed to start a process + UAC

Ok, I understand that there are perhaps tens of thousands of these posts, but I've not found one after an hour searching that seems to meet up with what I'm seeing.
Seeing this show up on a handful of servers, and I don't see the correlation with the servers having this issue and things they have in common. I'm seeing it on all of our Lync Front-End servers, and then on a few terminal servers. I'm going to give the
error for the Lync servers here though.
The process started at 9:00:25 AM failed to create System.PropertyBagData, no errors detected in the output. The process exited with 0
Command executed: "C:\Windows\system32\cscript.exe" /nologo "GetSQL2012DBFilesFreeSpace.vbs" "FE-05\RTCLOCAL" "FE-05.home.ku.edu" "RTCLOCAL"
Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 9359\180265\
One or more workflows were affected by this.
Workflow name: Microsoft.SQLServer.2012.Monitoring.DBFileSpaceMonitor
Instance name: tempdb2
Instance ID: {1FFB1DA7-414F-CAA1-E3EC-07AC097A2CED}
Management group: ITES
So since I've been working through all these little annoying warnings and trying to sort them out I decided to run the script.
<Collection><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.28
55484-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conve
rsionType>PerformanceData</ConversionType><Property Name="Database" VariantType=
"8">master</Property><Property Name="FileId" VariantType="3">1</Property><Proper
ty Name="FreeSpaceMB" VariantType="5">37646.0621050745</Property><Property Name=
"FreeSpacePercent" VariantType="5">99.9912017130836</Property><Property Name="Fr
eeSpaceAutoGrowMB" VariantType="5">0.6875</Property><Property Name="FreeSpaceAut
oGrowPercent" VariantType="5">17.1875</Property></DataItem><DataItem type="Syste
m.PropertyBagData" time="2014-06-04T09:23:23.2855484-05:00" sourceHealthServiceI
d="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</Conver
sionType><Property Name="Database" VariantType="8">master</Property><Property Na
me="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" VariantType
="5">39248.5533834203</Property><Property Name="FreeSpacePercent" VariantType="5
">99.9991440853338</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5
">0.414063</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">5
5.2084</Property></DataItem><DataItem type="System.PropertyBagData" time="2014-0
6-04T09:23:23.2905518-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDD
A89CEB89"><ConversionType>PerformanceData</ConversionType><Property Name="Databa
se" VariantType="8">tempdb</Property><Property Name="FileId" VariantType="3">1</
Property><Property Name="FreeSpaceMB" VariantType="5">36681.1775486072</Property
><Property Name="FreeSpacePercent" VariantType="5">99.9923331676945</Property><P
roperty Name="FreeSpaceAutoGrowMB" VariantType="2">0</Property><Property Name="F
reeSpaceAutoGrowPercent" VariantType="2">0</Property></DataItem><DataItem type="
System.PropertyBagData" time="2014-06-04T09:23:23.2905518-05:00" sourceHealthSer
viceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</C
onversionType><Property Name="Database" VariantType="8">tempdb</Property><Proper
ty Name="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" Varian
tType="5">38307.2356943516</Property><Property Name="FreeSpacePercent" VariantTy
pe="5">99.9940044295872</Property><Property Name="FreeSpaceAutoGrowMB" VariantTy
pe="2">0</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="2">0</
Property></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:
23:23.2915509-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89
"><ConversionType>PerformanceData</ConversionType><Property Name="Database" Vari
antType="8">tempdb</Property><Property Name="FileId" VariantType="3">3</Property
><Property Name="FreeSpaceMB" VariantType="5">39745.5</Property><Property Name="
FreeSpacePercent" VariantType="5">99.988679245283</Property><Property Name="Free
SpaceAutoGrowMB" VariantType="5">120.5</Property><Property Name="FreeSpaceAutoGr
owPercent" VariantType="5">96.4</Property></DataItem><DataItem type="System.Prop
ertyBagData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1
D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionTy
pe><Property Name="Database" VariantType="8">tempdb</Property><Property Name="Fi
leId" VariantType="3">4</Property><Property Name="FreeSpaceMB" VariantType="5">3
9746.375</Property><Property Name="FreeSpacePercent" VariantType="5">99.99088050
31447</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">121.375</Pr
operty><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">97.1</Property>
</DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.291
5509-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conver
sionType>PerformanceData</ConversionType><Property Name="Database" VariantType="
8">tempdb</Property><Property Name="FileId" VariantType="3">5</Property><Propert
y Name="FreeSpaceMB" VariantType="5">39745.875</Property><Property Name="FreeSpa
cePercent" VariantType="5">99.9896226415094</Property><Property Name="FreeSpaceA
utoGrowMB" VariantType="5">120.875</Property><Property Name="FreeSpaceAutoGrowPe
rcent" VariantType="5">96.7</Property></DataItem><DataItem type="System.Property
BagData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1D980
F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><
Property Name="Database" VariantType="8">tempdb</Property><Property Name="FileId
" VariantType="3">6</Property><Property Name="FreeSpaceMB" VariantType="5">39744
.875</Property><Property Name="FreeSpacePercent" VariantType="5">99.987106918239
</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">119.875</Propert
y><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">95.9</Property></Dat
aItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2915509-
05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionT
ype>PerformanceData</ConversionType><Property Name="Database" VariantType="8">te
mpdb</Property><Property Name="FileId" VariantType="3">7</Property><Property Nam
e="FreeSpaceMB" VariantType="5">39744.9375</Property><Property Name="FreeSpacePe
rcent" VariantType="5">99.9872641509434</Property><Property Name="FreeSpaceAutoG
rowMB" VariantType="5">119.9375</Property><Property Name="FreeSpaceAutoGrowPerce
nt" VariantType="5">95.95</Property></DataItem><DataItem type="System.PropertyBa
gData" time="2014-06-04T09:23:23.2915509-05:00" sourceHealthServiceId="9F1D980F-
BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Pr
operty Name="Database" VariantType="8">tempdb</Property><Property Name="FileId"
VariantType="3">8</Property><Property Name="FreeSpaceMB" VariantType="5">39742.2
5</Property><Property Name="FreeSpacePercent" VariantType="5">99.9805031446541</
Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">117.25</Property><
Property Name="FreeSpaceAutoGrowPercent" VariantType="5">93.8</Property></DataIt
em><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2915509-05:
00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType
>PerformanceData</ConversionType><Property Name="Database" VariantType="8">tempd
b</Property><Property Name="FileId" VariantType="3">9</Property><Property Name="
FreeSpaceMB" VariantType="5">39744.5625</Property><Property Name="FreeSpacePerce
nt" VariantType="5">99.986320754717</Property><Property Name="FreeSpaceAutoGrowM
B" VariantType="5">119.5625</Property><Property Name="FreeSpaceAutoGrowPercent"
VariantType="5">95.65</Property></DataItem><DataItem type="System.PropertyBagDat
a" time="2014-06-04T09:23:23.2975503-05:00" sourceHealthServiceId="9F1D980F-BA02
-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Proper
ty Name="Database" VariantType="8">model</Property><Property Name="FileId" Varia
ntType="3">1</Property><Property Name="FreeSpaceMB" VariantType="5">39630.875</P
roperty><Property Name="FreeSpacePercent" VariantType="5">99.9944806182969</Prop
erty><Property Name="FreeSpaceAutoGrowMB" VariantType="5">0.875</Property><Prope
rty Name="FreeSpaceAutoGrowPercent" VariantType="5">28.5714285714286</Property><
/DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.2975
503-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Convers
ionType>PerformanceData</ConversionType><Property Name="Database" VariantType="8
">model</Property><Property Name="FileId" VariantType="3">2</Property><Property
Name="FreeSpaceMB" VariantType="5">39248.5690084203</Property><Property Name="Fr
eeSpacePercent" VariantType="5">99.9991838953776</Property><Property Name="FreeS
paceAutoGrowMB" VariantType="5">0.429688</Property><Property Name="FreeSpaceAuto
GrowPercent" VariantType="5">57.2917333333333</Property></DataItem><DataItem typ
e="System.PropertyBagData" time="2014-06-04T09:23:23.3025532-05:00" sourceHealth
ServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData
</ConversionType><Property Name="Database" VariantType="8">msdb</Property><Prope
rty Name="FileId" VariantType="3">1</Property><Property Name="FreeSpaceMB" Varia
ntType="5">37585.1339389847</Property><Property Name="FreeSpacePercent" VariantT
ype="5">99.9579465372616</Property><Property Name="FreeSpaceAutoGrowMB" VariantT
ype="5">0.875</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5
">5.2434456928839</Property></DataItem><DataItem type="System.PropertyBagData" t
ime="2014-06-04T09:23:23.3025532-05:00" sourceHealthServiceId="9F1D980F-BA02-D35
1-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><Property N
ame="Database" VariantType="8">msdb</Property><Property Name="FileId" VariantTyp
e="3">2</Property><Property Name="FreeSpaceMB" VariantType="5">36542.9860732182<
/Property><Property Name="FreeSpacePercent" VariantType="5">99.9936081094063</Pr
operty><Property Name="FreeSpaceAutoGrowMB" VariantType="5">17.289063</Property>
<Property Name="FreeSpaceAutoGrowPercent" VariantType="5">88.0971363057325</Prop
erty></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:2
3.3075515-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><C
onversionType>PerformanceData</ConversionType><Property Name="Database" VariantT
ype="8">xds</Property><Property Name="FileId" VariantType="3">1</Property><Prope
rty Name="FreeSpaceMB" VariantType="5">39628.25</Property><Property Name="FreeSp
acePercent" VariantType="5">99.990537949132</Property><Property Name="FreeSpaceA
utoGrowMB" VariantType="5">4.25</Property><Property Name="FreeSpaceAutoGrowPerce
nt" VariantType="5">53.125</Property></DataItem><DataItem type="System.PropertyB
agData" time="2014-06-04T09:23:23.3085531-05:00" sourceHealthServiceId="9F1D980F
-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</ConversionType><P
roperty Name="Database" VariantType="8">xds</Property><Property Name="FileId" Va
riantType="3">2</Property><Property Name="FreeSpaceMB" VariantType="5">39630.109
375</Property><Property Name="FreeSpacePercent" VariantType="5">99.9952295493541
</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">6.109375</Proper
ty><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">76.3671875</Propert
y></DataItem><DataItem type="System.PropertyBagData" time="2014-06-04T09:23:23.3
135527-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><Conv
ersionType>PerformanceData</ConversionType><Property Name="Database" VariantType
="8">rtcdyn</Property><Property Name="FileId" VariantType="3">1</Property><Prope
rty Name="FreeSpaceMB" VariantType="5">199127.125</Property><Property Name="Free
SpacePercent" VariantType="5">99.9915262322741</Property><Property Name="FreeSpa
ceAutoGrowMB" VariantType="5">983.125</Property><Property Name="FreeSpaceAutoGro
wPercent" VariantType="5">98.3125</Property></DataItem><DataItem type="System.Pr
opertyBagData" time="2014-06-04T09:23:23.3135527-05:00" sourceHealthServiceId="9
F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceData</Conversion
Type><Property Name="Database" VariantType="8">rtcdyn</Property><Property Name="
FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" VariantType="5"
>15768.585938</Property><Property Name="FreeSpacePercent" VariantType="5">99.649
8100227502</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="5">1944.5
85938</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5">97.229
2969</Property></DataItem><DataItem type="System.PropertyBagData" time="2014-06-
04T09:23:23.3195540-05:00" sourceHealthServiceId="9F1D980F-BA02-D351-E3A6-2EDDA8
9CEB89"><ConversionType>PerformanceData</ConversionType><Property Name="Database
" VariantType="8">rtc</Property><Property Name="FileId" VariantType="3">1</Prope
rty><Property Name="FreeSpaceMB" VariantType="5">198878.4375</Property><Property
Name="FreeSpacePercent" VariantType="5">99.8666480034548</Property><Property Na
me="FreeSpaceAutoGrowMB" VariantType="5">734.4375</Property><Property Name="Free
SpaceAutoGrowPercent" VariantType="5">73.44375</Property></DataItem><DataItem ty
pe="System.PropertyBagData" time="2014-06-04T09:23:23.3195540-05:00" sourceHealt
hServiceId="9F1D980F-BA02-D351-E3A6-2EDDA89CEB89"><ConversionType>PerformanceDat
a</ConversionType><Property Name="Database" VariantType="8">rtc</Property><Prope
rty Name="FileId" VariantType="3">2</Property><Property Name="FreeSpaceMB" Varia
ntType="5">15659.34375</Property><Property Name="FreeSpacePercent" VariantType="
5">98.9594524140546</Property><Property Name="FreeSpaceAutoGrowMB" VariantType="
5">1835.34375</Property><Property Name="FreeSpaceAutoGrowPercent" VariantType="5
">91.7671875</Property></DataItem></Collection>
As you can see a boatload of data is returned, then I realized that my command prompt was running in admin mode. When I ran the same command not in admin mode, there was no data returned, which seems to fit with the error. The script ran but no data came
back.
So, my question is, should I disable UAC on all my front end servers? Or, is there a better runas account to use? I believe I chose the default LocalSystem for everybody since it doesn't require as much effort.
Any feedback is welcome :)
Jeffrey S. Patton Jeffrey S. Patton Systems Specialist, Enterprise Systems University of Kansas 1001 Sunnyside Ave. Lawrence, KS. 66045 (785) 864-0242 | http://patton-tech.com

The agent should use LocalSystem and it is very rare to use a different account to run the agent service. This is probably a need to configure a run as account to be used by the SQL Discovery. SQL Server 2012 is much more locked down than previous versions
of SQL, so unless you gave localsystem admin rights to your instance of SQL running on this box, this script will always come back with nothing. check out kevin holmans article on how to configure run as accounts for the SQL MP, to address this issue.
http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
hope this helps!
Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG)
Please remember to click “Mark as Answer” on the post that helps you!
my new blog om2012.wordpress.com

SCOM failed to start a process - logical disk checks

Hey, I'm getting started with SCOM 2012 R2 and I'm having some weird warning alerts reported for many Windows 2008 servers. If I close the alert, it just comes back a little later.
I tried to research it quite a bit but I'm not really even sure where to start because I'm so new to the product.
What is the best place to debug something like this? Any suggested parameters for the vbs file?
I followed a guide on testing wmi via wbemtest and it listed my drive letters.
Servers are fully windows updated.
Disabled antivirus scanning of the SCOM related processes and folders
I think the script is part of the Windows Logical Drives MP and my version is 1.2.1.5
I tried to find the .vbs file it references, but it is not anywhere on the machine generating the alert.
I exported the .vbs file file and unescaped it from the SCOM server but I have no idea what parameters it wants lol
The process started at 11:02:53 PM failed to create System.PropertyBagData.
Errors found in output:C:\Program Files\Microsoft Monitoring
Agent\Agent\Health Service State\Monitoring Host Temporary Files
1807\9626\CollectLogicalDiskStatistics.vbs(94, 9) (null): Data error (cyclic
redundancy check). Command executed:
"C:\Windows\system32\cscript.exe" /nologo "CollectLogicalDiskStatistics.vbs"
falseWorking Directory: C:\Program Files\Microsoft Monitoring
Agent\Agent\Health Service State\Monitoring Host Temporary Files
1807\9626\One or more workflows were affected by this.
Workflow name:
Windows.LogicalDrives.CollectFreeSpace.RuleInstance name:
C:Instance ID: {374D942F-352C-C10B-68D9-7A50C3C279E0}

Hi Shaddie,
Can you check that the Agent that is installed on the target system is Healthy?
What you could do as well, on the affected system, is stop the Microsoft Monitoring Agent service, and re-name the Health Service folder (located at C:\Program Files\System Center Operations Manager\Agent\Health Service State).
Re-name that folder, then restart the Microsoft Monitoring Agent service. This will cause the Agent to re-download the discovery and monitoring rules, etc.
Also, see the following TechNet article, even though it is for SCOM 2007, some of the steps might still apply: http://blogs.technet.com/b/kevinholman/archive/2009/06/29/getting-lots-of-script-failed-to-run-alerts-wmi-probe-failed-execution-backward-compatibility-script-error.aspx
Please remember to click “Mark as Answer” on the post that helps you.
AdinE MCSE, MCSA, MCITP, MCTS; (Specializing in System Center and Private Cloud)
LinkedIn: http://ca.linkedin.com/in/adinermie
Website: http://AdinErmie.Wordpress.com

Job failing after start of process chain

HI All
i have proces chain based on sm37 job....but the chain is stucking at the Start process of the Proces chian and the Start process is in yellow...
when i check the status of the job in sm37.. it is showing as cancelled and it is showing in Release status for the next day.
When i check the job log entries for the job, it is showing the below message:
Job started
Step001 started (program rsprocess, variant&00000, user id xxxxxx)
" Process ABAP, Variant Delete_SLA_sales_complete is not scheduled waiting for event RSPROCESS 4DYXXXXXXXXXXXXX "
job cancelled
How to solve the above issue...?

Hi,
Your process chain has been scheduled repeatedly by using Repeat Scheduling option in RSPC. Then the Start Variant will remain in yellow. You need to make the released job to scheduled by getting into Planning view.
Regards,
Suman
Edited by: Suman Chakravarthy on Dec 7, 2011 11:22 AM

Create Physical Standby fails

It looks like a script that runs, Exits in the middle.
I am able to test a disk dump and execute host commands on both the source and destination server.
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Apr 3 12:14:49 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved.
set echo off>Connected. GridTest>GridTest>GridTest>GridTest>GridTest> 2 3 4 5 6 7 8 9 10 11 12 13 Row count
: 1 Start printing spfile value: spfile# G:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SPFILEGridTest.ORA PL/SQL procedure successfully completed.
GridTest>Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options SQL*Plus
: Release 10.2.0.1.0 - Production on Thu Apr 3 12:14:50 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved.
CONNECT sys/#GridTest# AS SYSDBA;>ORA-01012: not logged on CONNECT sys/#GridTest# AS SYSDBA;>

Sounds like you are loosing the network connection between your OMS and
the standby target? Check the network.
Regards,
Porus.

Physical standby failed to start MRP process

Similar Messages

Maybe you are looking for