Warning: ORA-16829: fast-start failover configuration is lagging

Hi
I got waring for fast_start failover configuration
DGMGRL> show configuration
Configuration - activefailover_migdb
Protection Mode: MaxPerformance
Databases:
migdb - Primary database
Warning: ORA-16829: fast-start failover configuration is lagging
migdbdr - (*) Physical standby database
Warning: ORA-16829: fast-start failover configuration is lagging
Fast-Start Failover: ENABLED
Configuration Status:
WARNING
anybody please suggest solution for the same

Dear shd,
Please check the following link;
http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28419/d_dg.htm
*ORA-16829: lagging Fast-Start Failover configuration*
+DBMS_DG.INITIATE_FS_FAILOVER was invoked in a maximum performance fast-start failover configuration when the configuration was not in the user-specified redo lag limit.+
Oracle Error :: ORA-16829
fast-start failover configuration is lagging
Cause
The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property. As a result, a fast-start failover could not happen in the event of a primary database failure.
Action
Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully trasmitting redo data. If this condition persists consider raising the value of the FastStartFailoverLagLimit configuration property.
Ogan

Similar Messages

ORA-16820: fast-start failover observer is no longer observing this databa

Wem have primary and physical standby of Oracle 11.2 on linux 2.6.18-92.el5. For a reason of hardware resources, we want to run the Observer on the standby machine. Here I have several questions:
1) Is it supported to run Observer on the standby?
2) Does fast-start failover means automatical detecting down of primary and switch over the role automatically? WE do not want automatical switch over.
3) Started Observer on the standby and run show configuration, get errorDGMGRL> show configuration;
Configuration - antony
Protection Mode: MaxAvailability
Databases:
    rdev2 - Primary database
    sdev2 - (*) Physical standby database
      Error: ORA-16820: fast-start failover observer is no longer observing this database
Fast-Start Failover: ENABLED
Configuration Status:
ERROR Is the error caused by sunning Observer on standby, or other things?
Thanks.

Answering all your questions
Does fast-start failover means automatical detecting down of primary and switch over the role automatically? WE do not want automatical switch over.
Fast-Start Failover is an Oracle Data Guard 10g Release 2 feature that automatically, quickly, and reliably fails over to a designated, synchronized standby database in the event of loss of the production database, without requiring manual intervention to execute the failover.
In addition, following a fast-start failover, the original production database is automatically reconfigured as a new standby database upon reconnection to the configuration. This enables Data Guard to restore disaster protection in the configuration quickly and easily, returning the database to a protected state as soon as possible.
Is it supported to run Observer on the standby?
There are three essential participants in a Fast-Start Failover configuration:
• The production database
• A target standby database
• The Fast-Start Failover Observer
The target standby database will become the new production database following a fast-start failover (note: There can be multiple standby databases in a Data Guard configuration, but only one can be designated as the fast-start failover target. A manual failover would be required in order to execute a failover to any of the additional standby databases within the configuration).
The Observer is a separate process incorporated into the DGMGRL client that continuously monitors the production database and the target standby database for possible failure conditions.
The rule is that out of these three participants, (production database, standby database & observer) whichever two can communicate with each other will determine the outcome of fast-start failover
Hope the above explaination answers your question.

Data Guard Broker: errors ORA-16816 and ORA-16817 with Fast Start Failover

Hi,
my environment is:
OS: Windows XP Professional Edition SP2
DB: Oracle EE 10.2.0.3
Primary db: orcl
Standby db: stby
both databases are running on the same server.
I have configured Data Guard as described in the DG Administration Guide.
In the Data Guard Broker I switch to 'stby' succesfully and 'stby' is the primary db and 'orcl' is the standby db.
I switched back to 'orcl' as primary db and I get some errors:
DGMGRL> show database 'orcl' statusreport;
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* WARNING ORA-16817: configuration for Fast Start of Failover is not synchronized.
DGMGRL> show database 'stby' statusreport;
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* ERROR ORA-16816: wrong databaserole
* WARNING ORA-16817: configuration for Fast Start of Failover is not synchronized.
DGMGRL> show configuration;
Configuration
Name: DG1
Enabled: YES
Protection Mode: MaxAvailability
Fast-Start Failover: ENABLED
Databases:
orcl - Physical standby database
- Fast-Start Failover target
stby - Primary database
Current status for DG1:
Warning: ORA-16607: one or more databases failed.
I have searched for solutions on Metalink and google, but with no success.
Has anyone got this kind of problem?
Any suggestions on how to resolve it?
Thanks

Hi DigerDBA
I did your advice , the error disappear, and thanks for your advice , but do I need to keep standby_file_management='AUTO' or 'MANUAL' in primary and standby init files?
Am asking this because when I use the observer the failover failed and I get the following error
SQL Execution error=604, sql=[ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WAIT WITH SESSION SHUTDOWN]. See error stack below.
ORA-00604: error occurred at recursive SQL level 1
ORA-01275: Operation ADD LOGFILE is not allowed if standby file management is automatic.
Complete Failover operation failed in the step when attempting to convert the database to be the new primary.
Database Resource SetState Error (16771)
01/07/2014 09:14:43
Command FAILOVER TO epprod2 completed with error ORA-16771
if possible can you advice me please?

Fast Start Failover has broken my Logical Standby and Flashback has not helped

I have a primary ( PRIMARYP ), a physical standby ( STANDBYP ) and a logical standby ( STANDBYL ).
I configured Fast Start Failover ( with STANDBYP as the target ) and started an Observer. I did a shutdown abort on my primary and the Fast Start Failover did make STANDBYP the primary. I was able to reinstate PRIMARYP as a physical standby.
However when I checked my broker config it gave for STANDBYL
ORA-16795: the standby database needs to be recreated
Strange I though, since I would have expected STANDBYL to survive ok given that the new primary, STANDBYP was a physical standby of PRIMARYP.
Not to worry I thought, I simply will flashback STANDBYL to the beginning of the day and SQL APPLY will reapply all the redo.
This is where the problem begins
I mount STANDBYL
RMAN> connect target /
connected to target database: STANDBYL (DBID=440422466, not open)
RMAN> flashback database to time "TO_DATE('05/12/13 09:30:00','DD-MM-YY HH24:MI:SS')";
Starting flashback at 05-DEC-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=11 device type=DISK
starting media recovery
archived log for thread 1 with sequence 24 is already on disk as file /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_12_04/o1_mf_1_24_99yqwog0_.arc
archived log for thread 1 with sequence 25 is already on disk as file /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_12_05/o1_mf_1_25_9b0mlyvr_.arc
media recovery complete, elapsed time: 00:00:04
Finished flashback at 05-DEC-13
RMAN> quit
Recovery Manager complete.
oraclel[STANDBYL]>dgmgrl
DGMGRL for Linux: Version 11.2.0.3.0 - Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/manager
Connected.
DGMGRL> shutdown;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
DGMGRL>
DGMGRL>
DGMGRL> startup;
ORACLE instance started.
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
ORA-01589 - that a nasty surprise ! I didn't think I would need to do anything with the log sequences after a flashback
Any ideas of what is going on ?
thanks,
Jim

Hello;
This pdf might meet your needs :
http://blogs.oracle.com/AlejandroVargas/resource/DATAGUARD-FSFO-IMPLEMENTATION.pdf
Additional info :
http://oracle-tech.blogspot.com/2008/08/fast-start-failover-it-is-reliable.html
http://jakub.wartak.pl/blog/?p=80
http://www.databasejournal.com/features/oracle/article.php/3849106/Fast-Start-Failover-in-Oracle-11g-Data-Guard.htm
Best Regards
mseberg

Fast-Start Failover - Without Observer

Hello Experts,
I have a 3 node RCA with a 3node standby. Manual complete failover and switchover work correctly. I would like to enablr fast-start failover when nobody is around.
I know that according to the documentation, I would need a 3rd server to act like the observer. But I 've run out of servers.
Could someone provide clues or ideas how I could set this up. Do I indeed need an observer, or is it really just for additional fault tolerance?
Sincerely
Jan S.

There's no shortage of short notes on this :
http://jakub.wartak.pl/blog/?p=80
http://oracleinstance.blogspot.com/2010/01/configuration-of-10g-data-guard-broker.html
http://gjilevski.wordpress.com/2010/03/06/configuring-10g-data-guard-broker-and-observer-for-failover-and-switchover/
http://www.oracle.com/technetwork/articles/smiley-fsfo-084973.html
No idea how you would do it without Observer, its just a failover then.
Cooper

Can fast start failover be achieved in maximum performance mode

In a physical standby I would like to know if it is possible to configure High Availability in async mode to achieve fast-start failover? If so, please briefly describe how. Thanks

I've always said, size doesn't matter to Data Guard except when you are creating a standby database. After that it is the amount of Redo that is generated by the Primary database. A failover is a failover, for a 10GB database or for a 60TB database. The scary part is having to get the old Primary back up as a standby as quickly as possible.
Of course if the original Primary is completely toast then you have to recreate it with a new backup of the new primary or use a backup of the original Primary that happens to be on the Primary system and restore it as a standby and let Data Guard catch it up with the current state of affairs.
But, if the original Primary is still intact then you can use flashback database to reinstate it as a physical standby with little effort and no major backup restores. And of course, that is one of the requirements of Fast-Start Failover (FSFO). To enable it you have to have flashback database enabled on both the Primary and the FSFO target standby. Since enabling FB Database requires the database to be at the mount state I would suggest you enable it right after the upgrade to 11g.
When FSFO triggers a failover after a failure of the Primary, the Observer will automatically re-instantiate the failed Primary as a standby when it is started again and then it will be resynchronized with the new Primary automatically by Data Guard as normal.
The only difference between Maximum Availability FSFO and Maximum Performance FSFO is that you have to decide how much data you are will to lose when a failover occurs and tell the Broker by configuring the FastStartFailoverLagLimit property (see section 9.2.12 of the Broker manual).
You also want to be sure to place the Observer on a system where it is not affected by the Primary or Standby server going down or a network break between the Primary and the Standby. And if you can, use Grid Control. When you enable FSFO in Grid Control (on the Data Guard home page) you can specify 2 systems where the Observer can live. If it goes down on the original system an atempt will be made to restart it there. If that system if no longer available then Grid Control will attempt to start a new Observer on the 2nd system.
I would highly recommend you read the section [5.5 Fast-Start Failover|http://download.oracle.com/docs/cd/B28359_01/server.111/b28295/sofo.htm#i1027843] for lots of good information. And of course, the [Data Guard 11g Handbook|http://www.amazon.com/Oracle-Guard-Handbook-Osborne-ORACLE/dp/0071621113] (sorry, still plugging the book :^)
Larry

Protection Modes and Fast-Start Failover

Oracle Maximum Availability Architecture allows you to set fast-start failover (FSF)to automatically failover to the standby in the event of losing the primary database.
One condition of FSF is that it will only initiate if there is a guarantee of no data loss. This is where i start getting confused. Maximum Availability mode allows for data loss as the primary will still process transactions if the connection to the standby is lost. This means then in the event of the standby being out of sync with the primary database (i.e. network glitches) and then losing the primary database to hardware issues for example. FSF will not be able to initiate as data will be lossed and a complete loss of service will happen!
Can FSF be used in Maximum Protection mode as this will always mean FSF will be able to occur? Also what is the overhead towards the databases with regards to running them in this mode?
Thanks,
Chris

Hi,
Can FSF be used in Maximum Protection mode as this will always mean FSF will be able to occur? Yes, Maximum Protection Mode can be used with Fast-Start Failover, please review the next link.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/cli.htm#BABEIIHD
Also what is the overhead towards the databases with regards to running them in this mode?
Yes, the overhead is on major scale that other modes.
Regards.

Dataguard broker Warning: ORA-16610

Hi
Oracle 10g.
I just configured dataguard broker and followed all the steps in:
http://apunhiran.blogspot.com/2009/09/how-to-configure-data-guard-broker.html
However, I am constantly getting ORA-16610.
any idea, how to resolve this ?
DGMGRL> SHOW CONFIGURATION
Configuration
Name: CatalogDR
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
orclprd_wlg - Primary database
orclprd_akl - Physical standby database
Current status for "CatalogDR":
Warning: ORA-16610: command 'Broker automatic health check' in progress

Ah broker!
My friend calls it "data broken"
I have my setup notes I can post if you want. I had it working and I like its speed, but I found it to be a pain and went back to SQL for all my commands.
My offer to post my broker setup notes stands
mseberg
Later
John;
I checked my setup note and here's what i have on your current error :
ORA-16607 on SHOW CONFIGURATION
Problem: After creating your configuration and adding the standby database, you issued a SHOW CONFIGURATION as suggested. Instead of the expected SUCCESS, the report ends up with
Warning: ORA-16607: one or more databases have failed
. Checking with oerr ora 16607 was not very helpful (see above), and you neither can find anything in your alert.log nor any trace files.
Cause: Probably at least one of your databases is not using an SPFILE.
Solution: Check whether your databases have an SPFILE associated. It is usually located in $ORACLE_HOME/dbs/spfile$ORACLE_SID.ora. If it does not exist, create it: Login to your database as SYSDBA, and issue the command CREATE SPFILE FROM PFILE;. Even if it exists, to make the database using it you need to restart the instance - it must be used already at startup.Edited by: mseberg on Aug 11, 2011 8:12 PM

Error ORA-01460 warning ORA-01461 during running a mapping with parameters

Oracle 10g release2(10.2.0.1.0), OWB 10.2.0.1.31, Workflow server 2.6.4
I have a simple process flow ( start -> mapping -> end).
The mapping consists of 4 input groups(3 ordinary tables<INGRP1, INGRP2, INGRP3> and 1 mapping input parameter operator <INGRP4>), a joiner, a filter, an expression operator and 1 output group.
I want to use two variables in join condition, so I bound two mapping input parameters(<INGRP4.SRC_SYS_CDE> and <INGRP4.ADMIN_ORG_NUM>) with two parameters of the process flow's start activity.
Those two mapping input parameters are of type char, one is 4-char long and the other is 2-char long. So I set both of the two parameters of the start activity as String, one as 08, another as 7504.
My join condition is:
INGRP1.ORGIDT = INGRP2.SOURCEORGANIZATIONNO AND
INGRP2.SOURCESYSTEMCODE = INGRP4.SRC_SYS_CDE AND
INGRP2.ADMINORGANIZATIONNO = INGRP4.ADMIN_ORG_NUM AND
INGRP1.CURCDE = INGRP3.NUM(+)
There are no errors and warnings in validation, generation and deployment process, but when I run the process flow, it always finishes blankly(zero insert) with no error and warning messages. It should insert more than 20,000 rows.
When I run the mapping and set the parameters 08 and 7504 at the parameter prompt, then start, the following error and warning occurs.
Error ORA-01460: unimplemented or unreasonable conversion requested
Warning ORA-01461: can bind a LONG value only for insert into a LONG column
So what's the problem? How can I fix it?

The problem was mapping input parameter type.
VARCHAR2-type mapping input parameter works with String-type PF parameter. But CHAR-type won't.

Failover Configuration

For failover configuration with Oracle 9i I have used
two database in same m/c. and the listner.ora is as following :-
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC3))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = tcs052640)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oracle\ora_home)
(PROGRAM = extproc)
(SID_DESC =
(ORACLE_HOME = D:\oracle\ora_home)
(SID_NAME = SPACE)
(SID_DESC =
(ORACLE_HOME = D:\oracle\ora_home)
(SID_NAME = UIIVS2)
And TNS Entry which i have used in a m/c. which has only oracle client is like the following :-
PROD.WORLD =
(DESCRIPTION_LIST =
(FAILOVER = TRUE)
(LOAD_BALANCE = FALSE)
(DESCRIPTION =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = TCS052640)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = SPACE.WORLD)
(SERVER = DEDICATED)
(DESCRIPTION =
(ADDRESS =
(PROTOCOL = TCP)
(HOST = TCS052640)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = UIIVS2.WORLD)
(SERVER = DEDICATED)
Now i am connected to SPACE from that m/c. which has only Oracle 9i client and then shutdown the database SPACE, but
after shutting down client is not dynamically connecting to the database UIIVS2,though I have written "FAILOVER = TRUE" in tnsnames.ora.
It is giving error like :-
ORA-12571: TNS:packet writer failure
ORA-03114: not connected to ORACLE
& when I am attempting test connection it is giving error
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
What more I have to do for connecting dynamically UIIVS2 when SPACE is down.
If the database located in separated m/c. is there anything more need to do.
Thanks in advance.

Guys,
have successfully done the failover, the failover parameter should be ON in the tns entries - thanks a lot for all of ur help.
Regards,
Prasenjit

Enabling the Fast-Start Recovery Option

Using Oracle 10g R2, Standard Edition .
I'm trying to resize the redolog file using the redolog advisor from the Database console.Before that Oracle recommends to change the value of the parameter:
alter system set fast_start_mttr_target=300 scope=both , in order to be able
to use the redolog advisor sizing.
Unfortunately I got the following Error
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00439: feature not enabled: Fast-Start Fault Recovery
The database is running in NO ARCHIVE MODE
Thanks a lot

I don't have Metalink Account.
But I Have just read ( Oracle® Database Concepts 10g Release 1 (10.1)
Part Number B10743-01 )
see the follwing link
http://download-east.oracle.com/docs/cd/B14117_01/server.101/b10743/high_av.htm
that this feature is only available on Enterprise Edition.
But I'm using Standard Edition, so no way to go ahead

Error "can not start the configuration in parallel does not correct"

Hello everybody,
I have Windows 7 SP1, and when I install Business Objects 4.1 Client, it is install correctly but when i execute the program, for example BO Rich Client, an error appear "can not start the configuration in parallel does not correct" Could you help me?
Thanks in advance!

Check this KB
1678498 - BI 4.0 Universe Designer Gives Side-by-Side configuration incorrect Error

Error: ORA-16532: Data Guard broker configuration does not exist

Hi there folks. Hope everyone is having a nice weekend.
Anyways, we have a 10.2.0.4 rac primary and a 10.2.0.4 standby physical standby. We recently did a switchover and the dgbroker files automatically got created in the Oracle_home/dbs location of the primary. Now need to move these files to the common ASM DG. For this, I followd the steps from this doc:
How To Move Dataguard Broker Configuration File On ASM Filesystem (Doc ID 839794.1)
The only exception to this case is that I have to do this on a Primary and not a standby so I am disabling and enabling the Primary(and not standby as mentioned in below steps)
To rename the broker configuration files in STANDBY to FRA/MYSTD/broker1.dat and FRA/MYSTD/broker2.dat, Follow the below steps
1. Disable the standby database from within the broker configuration
DGMGRL> disable database MYSTD;
2. Stop the broker on the standby
SQL> alter system set dg_broker_start = FALSE;
3. Set the dg_broker_config_file1 & 2 parameters on the standby to the appropriate location required.
SQL> alter system set dg_broker_config_file1 = '+FRA/MYSTD/broker1.dat';
SQL> alter system set dg_broker_config_file2 = '+FRA/MYSTD/broker2.dat'
4. Restart the broker on the standby
SQL> alter system set dg_broker_start = TRUE
5. From the primary, enable the standby
DGMGRL> enable database MYSTD;
6. Broker configuration files will be created in the new ASM location.
I did so but when I try to enable the Primary back I get this:
Error: ORA-16532: Data Guard broker configuration does not exist
Configuration details cannot be determined by DGMGRL
Form this link,(Errors setting up DataGuard Broker it would seem that I would need to recreate the configuration....Is that correct ? If yes then how come Metalink is missing this info of recreating the configuration... OR is it that that scenario wouldnt be applicable in my case ?
Thanks for your help.

Yes I can confirm from the gv$spparameter view that the changes are effective for all 3 instances. From the alert log the alter system didnt throw u pany errros. I didnt restart the instances though since I dont have the approvals yet. But I dont think thats required.

I have LR 4 and now I cannot open the software because I get this warning: light room cannot start because it cannot create files in the temp file location.. C:/windows/temp. How do I fix this? I have removed and downloaded LR and even used by disc and st

I have LR 4 and now I cannot open the software because I get this warning: "light room cannot start because it cannot create files in the temp file location. C:\windows\temp\". I think I need to have LR open in a different place but I have no idea how to do that. Any help is most appreciated.
Alex

Jim
Thank you for your prompt reply. Unfortunately I am not that tech oriented and
cannot easily find that folder. I did notice when I was booting up the LR software
that I could accept the site where LR usually is set up or choose a place. I am
thinking that the standard location for LR software is corrupted and that if I
chose a different place it would work. I say this because whether I use my
original disc or download from adobe I get the same warning. I have 100GB of
memory on the hard drive and I have cleaned the computer with Mcaffee and free
software. What should I do next? I can't use this software and I doubt LR 5
would open up with my current problem.
Alex

Unable to start ICM Configuration Manager in ICM 8.5

Hi,
We are in the midst of setting the unified contact center 8.5.2 on windows server 2008 R2.
We are using CUCM 8.5. As for the icm 8.5.2, the servers are as follows:
1. Router A & logger A & CMPG A & VRU PG A on 1 mcs 7845
2. Router B & logger B & CMPG B & VRU PG B on 1 mcs 7845
3. Administration/ Data server with HDS on 1 mcs 7845
All servers are running ms SQL server 2005 with sp2. When the instance and all components
were created, I could start all services on these 3 servers. But when I tried to open the
Configuration Manager, it showed an error "(-9959) The AWDB needs to be reloaded before
any operations may be attempted. Please run Initialize Local Database."
Then I tried to start the process in the Initialize Local Database windows, it threw out
another error saying "the pipe has ended" following by another message "the process is
completed".
Then I tried o start the configuration manager or the script editor again, the same
problem still persists. I tried to recreate the Administration server & data server component again, but it
doesn't help. I also tried to delete the AWDB but it said the database in current in use.
Did I miss out any important steps here? Appreciate your help to rectify this issue ASAP.
I also noticed version 8.x and 7.5 is so much different. How do I check the each icm
process like the process window in version 7.5?
Thanks & regards,
Eric

Geoff is correct...and I would agree with David as well.
I will try to be more specific and answer both questions:
On Windows Server 2003, SQL Server 2005 Service Pack 3 or higher is the requirement.
On Windows Server 2008 R2, SQL Server 2005 Service Pack 4 or higher is the requirement.
The validation should be enforced in ICM Installer 8.0(1a).
Specifically, if SQL Server 2005 is detected on a machine and if the service pack is not minimally correct, when ICMCCInstaller version 8.0(1a) is run, the following severe error will be displayed to the user as well as being logged in the ICMInstall.log:
"[Error] Microsoft SQL Server 2005 installation does not have a high enough service pack. Cisco Unified ICM/Contact Center Enterprise & Hosted requires Microsoft SQL Server 2005 with Service Pack or greater."
where is 3 when running on Windows Server 2003 and 4 when running on Windows Server 2008 R2.
didn't you see this message when installing it?
The 8.0(1a) full installer contains the same file set as the 8.0(1) FCS version. The difference is in the InstallShield installer, which allows customers to install the product on Windows 2003 or Windows Server 2008 R2 (whereas the FCS version did not allow W2k8). Release 8.0(1a) completely replaces 8.0(1). End user documentation still just refers to 8.0(1) (i.e. you will not see reference to 8.0(1a)).
Note: 8.0(1a) does not have the complete working solution for Windows Server 2008 R2. You must apply the 8.5(2) or higher maintenance release in addition to 8.0(1a) to have a working solution. The MR contains bug fixes specific to Windows Server 2008 R2.
Now, how to see processes...well...say goodbye to that one as it is used to be
No UCCE Process Windows
In Windows Server 2008 R2, session 0, where Windows services run, has no desktop. No user can login to session 0 as previously known as console. And since there is no desktop, no visible object of any type can be displayed. Among such objects are the UCCE process windows. Customers and TAC have long relied on the process windows to diagnose the system and provide a feel good indicator that the system is running. The title bars of some windows are critical for determining things like which side is active. The tracing provided in some windows sometimes made it easier to diagnose or monitor certain conditions, especially in reproduction during a maintenance window. The goal was to make this same information available in another way.
Diagnostic Framework Portico: Process Status Info (title bar)
The status of the UCCE processes is used to be shown in the title bar of the corresponding process window. Since all UCCE process windows no longer show up in the taskbar, users are not able to use the process windows to check the status of the UCCE processes anymore. As a result, process status information was added to the Diagnostic Framework Portico.
The Diagnostic Framework Portico is a web-based GUI that list the current running UCCE processes.
You can also access the Diagnostic Framework Portico by choosing All Programs > Cisco Unified CCE Tools > Diagnostic Framework Portico.
Note that the process status information is now displayed. Additionally status changes and low uptime is highlighted. Uptime will be red if uptime is less than 10 minutes and yellow less than 30 minutes. These will also be underlined. This will help to identify cycling services. Status changes will be highlighted and made bold when a process's status changes. This highlighting will last for 10 minutes or until the status returns to its original state. Also as compared to the original page, the vertical space has been used more efficiently to fit more processes on a single page without scrolling. There is also a refresh checkbox which when checked will refresh the page every 5 seconds. It is checked by default.
EMSMon: Process EMS Messages
In Release 8.5(2), for Windows 2008, process windows for ICM processes are no longer available. The title bar status information is available in the Diagnostic Portico; however, real time data does not appear there. To address this, Cisco recommends that partners and TAC use EMSMON as a replacement.
EMSMON has been with UCCE/ICM since the earliest versions of ICM. EMSMON displays logged messages from a process as they are logged. It displays the same content as the former process windows. The two exceptions are the title bar and stdout and stderr output. Events are logged for all processes and appear in EMSMON. However, rare error condition messages (shelled processes, and so on) that go to stdout do not appear in an EMSMON window.
You can start EMSMON while the process is up or down. If the process is down, EMSMON displays messages from the process when the process starts. EMSMON does not end when the process ends. To end EMSMON, press CTRL+C or close the window.
Note: To prevent ICM processes from queueing too many EMSMON messages and exceeding the system memory, ICM processes may drop queued EMSMON messages. If this happens, EMSMON clients display a message indicating one of the clients fell behind and there is a gap. This message is also logged in the processes event log. This can happen if a particular EMSMON client is too slow or paused by quick edit or ctrl/s for example.
How to run EMSMON
EMSMON has the same parameters as procmon:
*Instance/Customer Node process,[process] [System]
The System parameter is optional. You can use it to run EMSMON from a machine remote from where the process is running.
For example, if the Instance/Customer Node is ?ucce and you want to monitor the JTAPI gateway on PG1A, type the following:
EMSMON ucce PG1A jgw1
If you are remote and the machine name is UCCEPG1A, type:
EMSMON ucce PG1A jgw1 UCCEPG1A
Note: A trust relationship must exist between the two machines. (Use the “NET USE” command or something similar).
The following list includes some EMSMON facts:
EMSMON (like DUMPLOG) can monitor multiple processes. The use of EMSMON to monitor multiple processes is not discussed here.
A single EMSMON can monitor multiple processes and merge their output (for example, (jgw1 and pim1).
Multiple EMSMONs can watch a single process. For example, you can have a local (on box) EMSMON and a remote EMSMON. Cisco recommends that you use one EMSMON only for each process.
To reserve system resources for ICM processes, it is recommended that you run the EMSMON client on a remote machine that does not host ICM processes. For example, running EMSMON client on side A of a PG and connecting it to a process on side B of a PG is not recommended.
To run EMSMON on a remote machine, copy emsmon.exe, emsmon.pdb, and icrmessages.dll from c:\icm\bin and place them on a remote machine.
You can cut and paste just as in the command windows but it is safer in EMSMON.
You can start EMSMON at anytime, even when the process is not running. (You can have a batch file on a machine to start sessions.)
For history (events prior to EMSMON starting), use DUMPLOG.
To change the number of lines each EMSMON window retains, modify the command window parameters.
With EMSMON, you can have one local connection and five remote connections per process. When the number of connections is exceeded, the oldest session is disconnected with the following message ?You are being disconnected because another user has connected to this named pipe.
If your system is running a heavy call load, your EMSMON connections may disconnect and the following message appears: ? You are being disconnected because the system is running a heavy call load; this connection may impact the performance of the system. It is recommended that you do not reconnect your EMSMON sessions until your system returns to a normal call load
Thanks,
Goran
Please rate with 5 stars if you find this post useful.

Warning: ORA-16829: fast-start failover configuration is lagging

Similar Messages

Maybe you are looking for