Registering recovery catalog in Enterprise Manager

Hi,
I created recovery catalog database successfully using RMAN of 10g R2 on command prompt. Every thing seems working fine on RMAN but when I connect to target database using EM and click the recovery catalog link, it does not show me the configured recovery catalog. When I try to configure the catalog, it gives me the error message "Bad Packet". I dont what the problem is. Can any one help me with this?

Hi,
I am using winXP and using EM DB of Oracle 10g. I used RMAN on command prompt and created recovery catalog by creating a recovery catalog user and assigning a catalog user to it. I have also registered target database with recovery catalog. Now all this is working on command prompt using RMAN utility. Both target and recovery are on one computer. Now when I try to see recovery catalog in EM DB, its says no recovery catalog has been configured and when I try to configure recovery catalog, following error message keeps coming
Validation Error
Examine and correct the following errors, then retry the operation:
Error - java.sql.SQLException: Io exception: Bad packet type
*Host--------- shahnawaz 
* Port---------5500
* SID-----------qasimdb
* Recovery Catalog Username-----zee
* Recovery Catalog Password------zee
I hope my question is quite clear. If you need more info. just let me know please. I will appreciate.
regards,
Qasim

Similar Messages

  • Register Oracle XE to Enterprise Manager

    Hi,
    I am interested to try oracle 10g XE and I've install it (My OS = Windows XP) but there's no enterprise manager for it. Can we use enterprise manager from another oracle 10g edition? if we can, how to do that?
    thanks
    tatang

    Hello,
    Are you sure the service OracleService(sid) has not been created? Can you check it?
    If it was not created, you could try to create it manually with this command:
    emca -config dbcontrol db -repos create
    and follow the instructions. Be sure to have the listener up at all times.
    Another option could be to recreate de database with dbca and it should create the service automatically.
    I haven´t had the chance to work with XE, but I guess it is the same concept as SE and EE.

  • V10.2.0.5 and Database Target Recovery Catalog Assignments

    We recently upgraded to version from version 10.2.0.4 to 10.2.0.5. After, I started to continue where I left off with assigning recovery catalogs to our database targets. What was a simple process previously, is now becoming a headache. First, when adding an already registered recovery catalog I received this message "The specified username does not match the recovery catalog username configured for this database.". I was then told by support to update the back-end repository tables to make the recovery catalog username lowercase. This didn't work so I removed the registered catalog and attempted to add it back. Then I received this message which is rather frightening:
    "In this version of Enterprise Manager, recovery catalog settings are now specific to each Enterprise Manager user. Existing recovery catalog settings made prior to upgrading Enterprise Manager have been preserved in order to allow existing backup jobs to continue to work. However, if you change the recovery catalog setting for this database, all non-user-specific settings will be removed, and each Enterprise Manager user that manages this database will have to individually reset their recovery catalog settings for this database. Do you want to continue?"
    I can't find any mention of this change in any updated documentation, support page, or other. Essentially, this tells me that as of GC version 10.2.0.5, assignment of a recovery catalog to a given database target is no longer centralized but de-centralized. Each user with OEM GC now has to assign a recovery catalog to each database instance irregardless if their profile is setup as a Super Admin. Or, if you expect to run a manaul backup for a given database you have to log in under a shared account which has all the catalogs assigned which defeats the purpose of any SAS 70 auditing.
    I have a ticket in with Oracle support at this time. If anyone has any insight to this I would love to know the reasoning behind it. Thanks.

    Well, product development responded with this:
    "The catalog management model has been changed in 10.2.0.5GC to
    accommodate new database catalog features and enhance security.
    Each team member would have to register the catalog separately for the
    targets they manage, through their own EM account. This is a one-time
    activity. Once that is done, the functionality is the same as before."
    What a huge faux pas.

  • Create a recovery catalog by using the Enterprise Manager Console

    Dear Sirs:
    I am using the Oracle9i database release 2. After installing the management server and running the Enterprise Manager Configuration Assistant, there was no recovery catalog and no CATTBS tablespace created. According to the Help and to your documentation entitled “Oracle Enterprise Manager Configuratrion Guide” this recovery catalog and CATTBS tablespace should be created automatically.
    Of course I am not running any target database on the same machine.
    How can I create a recovery catalog by using the Enterprise Manager Console, and not by using the rman command prompt?
    Please its urgent and I need an answer as soon as possible.
    Thank you in advance with best regards

    Dear Sir:
    Thank you very much for your reply, but unfortunately it didn’t help me. This article is repeating what is mentioned in the Help and the documents that I downloaded earlier. As I said earlier I know how to setup the recovery catalog by using the rman command prompt, but I couldn’t do it by using the Oracle Enterprise Manager Console. By using the wizards it is supposed to be created automatically but nothing of this happened.
    Please I need help urgently.

  • Recovery Failure in Oracle enterprise manager

    Hi ,
    When i tried to recover the whole database by selecting "Recover to the current time or a previous point-in-time" in Perform recovery area.
    It came up with the error message as shown below.
    ERROR :::::
    startup mount
    shutdown immediate
    shutdown immediate
    SQL*Plus: Release 11.2.0.1.0 Production on Tue Jun 1 14:45:44 2010
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    SQL> SQL> Connected.
    SQL> SQL> SQL> Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning option
    startup mount
    SQL*Plus: Release 11.2.0.1.0 Production on Tue Jun 1 14:46:45 2010
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    SQL> SQL> Connected to an idle instance.
    SQL> SQL> ORACLE instance started.
    Total System Global Area 2137886720 bytes
    Fixed Size 2215064 bytes
    Variable Size 1677722472 bytes
    Database Buffers 452984832 bytes
    Redo Buffers 4964352 bytes
    Database mounted.
    SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning option
    Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jun 1 14:46:50 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN>
    connected to target database: SPPADEV (DBID=1558297262, not open)
    using target database control file instead of recovery catalog
    RMAN>
    echo set on
    RMAN> run {
    2> restore database until time "to_date('2010-05-20 20:00:00', 'YYYY-MM-DD HH24:MI:SS')";
    3> recover database until time "to_date('2010-05-20 20:00:00', 'YYYY-MM-DD HH24:MI:SS')";
    4> }
    Starting restore at 01-JUN-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=452 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=3 device type=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: SID=32 device type=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: SID=62 device type=DISK
    creating datafile file number=1 name=/u02/oradata/SPPADEV/system01.dbf
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/01/2010 14:46:52
    ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '/u02/oradata/SPPADEV/system01.dbf'
    RMAN> exit;
    Recovery Manager complete.
    Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jun 1 14:46:52 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN>
    connected to target database: SPPADEV (DBID=1558297262, not open)
    using target database control file instead of recovery catalog
    RMAN>
    echo set on
    RMAN> alter database open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 06/01/2010 14:46:53
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    RMAN> exit;
    Recovery Manager complete.
    Recovery Manager: Release 11.2.0.1.0 - Production on Tue Jun 1 14:46:53 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN>
    connected to target database: SPPADEV (DBID=1558297262, not open)
    using target database control file instead of recovery catalog
    RMAN>
    echo set on
    RMAN> alter database open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 06/01/2010 14:46:53
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    RMAN> exit;
    Recovery Manager complete.
    It will be very much grateful if some one can help me with this issue.
    Thanks,
    Hary

    I see the error: ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '/u02/oradata/SPPADEV/system01.dbf'
    Does oracle have the rights to create that file there?

  • How to find databases registered in recovery catalog!

    I want to know how many databases registered in recovery catalog
    How can i find it?
    Thank you!

    Log in as your catalog owner and execute select distinct db_name from dbinc; with this you will see all registered databases , In 11G onwards as virtual catalog owner you will only see the databases on which you have been granted access.
    Regards
    Karan

  • Registering Clone database in Recovery catalog

    Can we able to register the clone database in recovery catalog database without changing dbid?
    I don't want to use dbid utility.
    Is that any parameter?
    Regards,
    Latha

    Well you can register it without changing any parameters in oracle 10.2
    That does not mean you should do it.
    I would have answered as follows:
    It is not a good idea to register a clone database in the same recovery catalog as the original database as the recovery catalog uses the dbid to identify the database and having two databases with the same dbid essentially corrupts the recovery catalog.
    If you change the dbid then it is perfectly okay to store the cloned database in the same recovery catalog.

  • Registering DB in Recovery Catalog

    how i can register DBs in Recovery Catalog, send commands plz

    I'm very slow... Last time I was, remember, I am trying to pick up :)
    Daljit Singh

  • OEM 10g - Upgrade Recovery Catalog

    Hello All,
    I'm experiencing some difficulties when trying to upgrade my recovery catalog using Oracle's Enterprise Manager 10g and wanted to see if anyone could explain this error.
    "+Error - Unable to retrieve the URL from repository. Check the specified target name and its corresponding target type. Other possible causes: remote EMD is not pointing to the web server, or remote target information has not bee loaded+."
    What URL is the repository trying to use? Do I need to reinstall my repository using emca? Any assistance is appreciated.
    Oracle DB Version: 10.2.0.3.0
    Catalog DB Version: 10.2.0.1.0
    OS: MS Windows Server 2003 SP2

    I perform the following tasks:
    <ol><li>Log in as sysdba</li>
    <li>Click the Maintenance Tab</li>
    <li>Click Recovery Catalog Settings (my recovery catalog is already registered)</li>
    <li>Click on Recovery Catalogs (located under Related Links)</li>
    <li>Select my recovery catalog and click Upgrade</li>
    <li>Put in my OS user credentials and Recovery Cataloge credentials and click OK</li>
    </ol>
    The error occurs when after I click OK.

  • Config recovery catalog database

    dear all.
    i had read several documents about "create recovery catalog", but all of that start with statement
    CREATE TABLESPACE
    ...and continue with CREATE USER, etc.
    I want to create a NEW database for recovery catalog, this database what characteristics must to have ?? Anyone have a link or document where explain me how to create a database (only i need database creation) for recovery catalog.???
    thanks
    The version is ORacle 10gr2

    hi,
    the recovery catalog is just a normal database with a schema called rman or whatever you choose.
    it should ideally be on a separate server to your target database. The RMAN database as with any other database should have multiplexed control files and redo files.
    schema creation assumming windows O/S
    -- Create tablepsace to hold repository
    CREATE TABLESPACE "RMAN"
    DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
    AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
    EXTENT MANAGEMENT LOCAL
    SEGMENT SPACE MANAGEMENT AUTO;
    -- Create rman schema owner
    CREATE USER rman IDENTIFIED BY rman
    TEMPORARY TABLESPACE temp
    DEFAULT TABLESPACE rman
    QUOTA UNLIMITED ON rman;
    GRANT connect, resource, recovery_catalog_owner TO rman;
    then create the recovery catalog
    C:>rman catalog=rman/rman@w2k1
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to recovery catalog database
    recovery catalog is not installed
    RMAN> create catalog tablespace "RMAN";
    recovery catalog created
    RMAN> exit
    Recovery Manager complete.
    C:>
    then register your database
    C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to target database: W2K2 (DBID=1371963417)
    connected to recovery catalog database
    RMAN> register database;
    database registered in recovery catalog
    starting full resync of recovery catalog
    full resync complete
    RMAN>
    let us know how you get on.
    rgds
    alan

  • Maintenance Recovery Catalog

    How can I remove the recovery catalog (registration of the metadata) made a backup on a tape that no longer exists on the host?
    RMAN> list backupset 65045;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    =========================================================
    65045 Full 122M SBT_TAPE 00:13:52 26-MAR-07
    BP Key: 65047 Status: UNAVAILABLE Tag: TAG20070326T112147
    Piece Name: g3idiv2b_1_1
    List of Datafiles in backup set 65045
    File LV Type Ckp SCN Ckp Time Name
    =========================================================
    4 Full 15154846192 26-MAR-07 /DATA/oradata/momina/example01.dbf
    RMAN> delete backupset 65045;
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=285 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=295 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 11/19/2008 08:40:09
    RMAN-06160: no backup pieces found for backup set key: 65045
    This error is obvious, I can not delete a backup tape to have a channel to disk.
    But implementing this
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    RMAN> CONFIGURE DEFAULT DEVICE TYPE TO sbt;
    old RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    new RMAN configuration parameters:
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete
    released channel: ORA_DISK_1
    released channel: ORA_DISK_2
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    RMAN> delete backupset 65045;
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=285 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=295 devtype=DISK
    released channel: ORA_DISK_1
    released channel: ORA_DISK_2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 11/19/2008 08:47:31
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 2
    If possible delete the backupset of recovery catalog despite not having media managemnet library (dont have hardware or sofware tape)?
    Juan

    Thank, but....
    With the channel disk:
    #> rman target / catalog rman/rman@database1
    RMAN> crosscheck backupset;
    Recovery Manager: Release 9.2.0.6.0 - 64bit Production
    RMAN>
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=175 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=285 devtype=DISK
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/DATA/backups/momia/3491_1_MOMIA_17_11_2008 recid=5524 stamp=671060706
    crosschecked backup piece: found to be 'AVAILABLE'
    Crosschecked 14 objects
    The backupset i need delete (of the recovery catalog) is register on tape.
    With the channel sbt:
    Recovery Manager complete.
    #> rman target / catalog rman/rman@database1
    RMAN> CONFIGURE DEFAULT DEVICE TYPE TO sbt;
    RMAN> crosscheck backupset;
    RMAN>
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=179 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=272 devtype=DISK
    released channel: ORA_DISK_1
    released channel: ORA_DISK_2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of crosscheck command at 11/19/2008 10:32:37
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    **ORA-27211: Failed to load Media Management Library**
    Additional information: 2
    The problem is the same.

  • Enterprise Manager Newbie Q's

    Greetings All,
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    Windows 2008 R2Last night one of the production users received an ORA-01652: unable to extend temp segment by 128 in tablespace TEMP error.
    Hence, my manager has requested that I
    “Please configure our database servers to notify us via email when critical thresholds are exceeded.
    This is a standard config option within enterprise manager”.I have very little experience/exposure with EM. In fact I’ve found several terms that I think all refer to the same thing (correct me if I’m wrong please), for example : "OEM Database Control", "OEM Grid Control", and something called "The Business Service Management (BSM)" capabilities of Oracle Enterprise Manager.
    Are these different products/tools, or different implementations of the OEM?
    We are not a RAC shop; Is the term GRID is also used to indicate a RAC environment?
    I am looking for some good "How To Use/Configure OEM" sources of information. Any suggestions would be appreciated.
    I’m looking a purchasing the following books, any recommendations on these or others?
    Oracle Enterprise Manager 10g Grid Control Handbook (Oracle Press) - Werner De Gruyter
    Oracle Enterprise Manager Grid Control 11g R1: Business Service Management - Ashwin Kumar Karkala, Govinda Raj Sambamurthy
    It seems that there is a data repository for the OEM. Is this generally required? Can I set things up such that I can get e-mail notifications when tablespace(s) exceed a certain usage threshold without the repository?
    I know I’ve rambled about some, thanks for your patients.
    Thanks for your time,
    Bob

    I can answer a couple of your questions...
    "OEM Database Control" is essentially "Oracle Enterprise Manager for a single database". "OEM Grid Control" (or, the current release, "OEM Cloud Control" is essentially "Oracle Enterprise Manager for several databases", plus the ability to monitor server hosts, web applications, and quite a few other non-database items. They are similar, but different products. Database Control generally gets installed along with the database software itself, while Grid/Cloud Control is a completely separate installation of a standalone product. I have no idea what the BSM bit refers to.
    Database Control uses the one monitored database as its data repository (in the SYSMAN schema). Grid Control also requires a repository, but you are allowed to install a separate database, without additional licensing fees, to serve as the repository for Grid Control so long as you don't use it for anything else (other than as an RMAN recovery catalog). If you don't want to install another database to serve Grid/Cloud Control, you can use an existing database, but it's generally not recommended.
    Neither Database Control nor Grid/Cloud Control will function without a repository. Either of them will allow you to set up alert notifications when tablespace(s) exceed your configured thresholds, or when various other events occur (DB shuts down, filesystem getting full, CPU load too high, too many sessions, whatever you like).
    The term "Grid" is used in "Oracle Grid Infrastructure", which is part of the clustering package that supports RAC. "Grid" is just a marketing term there, RAC and Grid Control are orthogonal concepts, neither requires the other but they can also be used together.
    I can't comment on the books.

  • RMAN-06428 recovery catalog is not installed

    RDBMS Version: 8.1.6
    Operating System and Version: sun sparc 5.8
    Error : RMAN-06428 RMAN-06428 recovery catalog is not installed
    Product (i.e. SQL*Loader, Import, etc.): RMAN
    Product Version: 8.1.6
    Hi,
    I hv a database running in unix box 1 (say 'FAST')
    and Im trying to install a recovery catalog database in unix box
    2
    (Rcat)
    1) in unixbox2..I hv created a new database, and I hv created a
    tablespace rcvcat and user rman .granted catalog_recovery_owner
    to rman.
    also I hv created a catalogue using this command
    create catalogue tablespace rcvcat;
    (no error logs generated)
    2)now when I try to connect to the catalogue I am getting an
    error
    what I did is, I tried connecting to rman of target database
    (FAST database)
    % rman target /catalog rman/rman@rcat
    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN-06005: connected to target database: FAST (DBID=3819569154)
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    also I tried like this,
    % rman target system/manager@fast catalog rman/rman@rcat
    Recovery Manager: Release 8.1.6.0.0 - Production
    RMAN-06005: connected to target database: FAST (DBID=3819569154)
    RMAN-06008: connected to recovery catalog database
    RMAN-06428: recovery catalog is not installed
    I dont understand why it says recovery catalog not installed ,
    when I hv created one in rcat database.
    Can anyone help me how to connect to catalog and register my
    database (I mean from which machine I need to run the commands)
    Thanks
    Venkat

    You do have a problem. It seems your "Shift" key is stuck.
    Anyway, please read: [ID 188682.1],
    Have a nice day.

  • Recovery Catalog showing wrong Archive Destination

    Hi All,
    I am using Oracle 10g on Solaris 10.
    The problem I am facing is this, while taking backup using recover catalog..............
    Starting backup at 27-JUL-11
    current log archived
    released channel: ch00
    released channel: ch01
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 07/27/2011 11:16:47
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    ORA-19625: error identifying file /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    This is because of the following reason
    RMAN> list archivelog all;
    List of Archived Log Copies
    Key Thrd Seq S Low Time Name
    39401 1 1567 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1567_756523261.dbf
    39402 1 1568 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1568_756523261.dbf
    39403 1 1569 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1569_756523261.dbf
    39404 1 1570 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1570_756523261.dbf
    39405 1 1571 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1571_756523261.dbf
    39406 1 1572 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1572_756523261.dbf
    39407 1 1573 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1573_756523261.dbf
    39408 1 1574 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1574_756523261.dbf
    39409 1 1575 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1575_756523261.dbf
    39410 1 1576 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1576_756523261.dbf
    39411 1 1577 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1577_756523261.dbf
    39412 1 1578 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1578_756523261.dbf
    39413 1 1579 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1579_756523261.dbf
    39414 1 1580 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1580_756523261.dbf
    39415 1 1581 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1581_756523261.dbf
    39416 1 1582 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1582_756523261.dbf
    39417 1 1583 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1583_756523261.dbf
    39418 1 1584 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1584_756523261.dbf
    39419 1 1585 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1585_756523261.dbf
    39420 1 1586 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1586_756523261.dbf
    39421 1 1587 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1587_756523261.dbf
    39422 1 1588 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1588_756523261.dbf
    39423 1 1589 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1589_756523261.dbf
    39424 1 1590 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1590_756523261.dbf
    39425 1 1591 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1591_756523261.dbf
    39426 1 1592 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1592_756523261.dbf
    39427 1 1593 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1593_756523261.dbf
    39428 1 1594 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1594_756523261.dbf
    39429 1 1595 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1595_756523261.dbf
    39430 1 1596 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1596_756523261.dbf
    39431 1 1597 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1597_756523261.dbf
    39432 1 1598 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1598_756523261.dbf
    39433 1 1599 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1599_756523261.dbf
    39434 1 1600 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1600_756523261.dbf
    39435 1 1601 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1601_756523261.dbf
    39436 1 1602 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1602_756523261.dbf
    39437 1 1603 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1603_756523261.dbf
    39438 1 1604 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1604_756523261.dbf
    39439 1 1605 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1605_756523261.dbf
    39440 1 1606 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1606_756523261.dbf
    39441 1 1607 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1607_756523261.dbf
    39442 1 1608 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1608_756523261.dbf
    39443 1 1609 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1609_756523261.dbf
    39444 1 1610 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1610_756523261.dbf
    39445 1 1611 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1611_756523261.dbf
    39446 1 1612 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1612_756523261.dbf
    39447 1 1613 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1613_756523261.dbf
    39448 1 1614 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1614_756523261.dbf
    39449 1 1615 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1615_756523261.dbf
    39450 1 1616 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1616_756523261.dbf
    39451 1 1617 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1617_756523261.dbf
    39452 1 1618 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1618_756523261.dbf
    39453 1 1619 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1619_756523261.dbf
    39454 1 1620 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1620_756523261.dbf
    39455 1 1621 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1621_756523261.dbf
    39456 1 1622 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1622_756523261.dbf
    39457 1 1623 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1623_756523261.dbf
    39458 1 1624 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1624_756523261.dbf
    39459 1 1625 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1625_756523261.dbf
    39460 1 1626 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1626_756523261.dbf
    39461 1 1627 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1627_756523261.dbf
    39462 1 1628 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1628_756523261.dbf
    39463 1 1629 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1629_756523261.dbf
    39464 1 1630 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1630_756523261.dbf
    39465 1 1631 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1631_756523261.dbf
    39466 1 1632 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1632_756523261.dbf
    39467 1 1633 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1633_756523261.dbf
    39468 1 1634 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1634_756523261.dbf
    39469 1 1635 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1635_756523261.dbf
    39470 1 1636 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1636_756523261.dbf
    39471 1 1637 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1637_756523261.dbf
    39682 1 1638 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1638_756523261.dbf
    39689 1 1639 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1639_756523261.dbf
    40642 1 1640 A 26-JUL-11 /oradb2/Archive/HCSPRD91/1_1640_756523261.dbf
    40643 1 1641 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1641_756523261.dbf
    40644 1 1642 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1642_756523261.dbf
    40645 1 1643 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1643_756523261.dbf
    40646 1 1644 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1644_756523261.dbf
    40647 1 1645 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1645_756523261.dbf
    40648 1 1646 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1646_756523261.dbf
    41310 1 1647 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1647_756523261.dbf
    41317 1 1648 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1648_756523261.dbf
    41373 1 1649 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1649_756523261.dbf
    41374 1 1650 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1650_756523261.dbf
    41375 1 1651 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1651_756523261.dbf
    41383 1 1652 A 27-JUL-11 /oradb2/Archive/HCSPRD91/1_1652_756523261.dbf
    *38725 1 56 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_56_757089402.dbf*
    *38946 1 57 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_57_757089402.dbf*
    *39000 1 58 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_58_757089402.dbf*
    *39022 1 59 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_59_757089402.dbf*
    *39243 1 60 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_60_757089402.dbf*
    *39297 1 61 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_61_757089402.dbf*
    *39703 1 62 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_62_757089402.dbf*
    *39704 1 63 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_63_757089402.dbf*
    *39705 1 64 A 26-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_64_757089402.dbf*
    *39933 1 65 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_65_757089402.dbf*
    *39991 1 66 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_66_757089402.dbf*
    *40023 1 67 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_67_757089402.dbf*
    *40024 1 68 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_68_757089402.dbf*
    *40025 1 69 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_69_757089402.dbf*
    *40254 1 70 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_70_757089402.dbf*
    *40308 1 71 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_71_757089402.dbf*
    *40345 1 72 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_72_757089402.dbf*
    *40570 1 73 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_73_757089402.dbf*
    *41329 1 74 A 27-JUL-11 /u01/oracle/product/10.2.0/db_1/dbs/arch1_74_757089402.dbf*
    I dont know from where recovery catalog is getting the information in bold.
    I have crosschecked and deleted archives and resynced the catalog several times. Immediatly after doing that the backup works fine, but the other day its the same thing all over again.
    Can some one tell me from where the catalog is getting this wrong infomation about archivelogs???
    By the way here is some more info about my target Database:
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /oradb2/Archive/HCSPRD91
    Oldest online log sequence 1651
    Next log sequence to archive 1653
    Current log sequence 1653
    NAME TYPE VALUE
    archive_lag_target integer 0
    log_archive_config string
    log_archive_dest string
    log_archive_dest_1 string LOCATION=/oradb2/Archive/HCSPR
    D91
    log_archive_dest_10 string
    log_archive_dest_2 string
    log_archive_dest_3 string
    log_archive_dest_4 string
    log_archive_dest_5 string
    log_archive_dest_6 string
    NAME TYPE VALUE
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string enable
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string enable
    log_archive_dest_state_3 string enable
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    log_archive_dest_state_7 string enable
    NAME TYPE VALUE
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable
    log_archive_duplex_dest string
    log_archive_format string %t_%s_%r.dbf
    log_archive_local_first boolean TRUE
    log_archive_max_processes integer 2
    log_archive_min_succeed_dest integer 1
    log_archive_start boolean FALSE
    log_archive_trace integer 0
    remote_archive_enable string true
    standby_archive_dest string ?/dbs/arch
    Regards .....

    Do you have any other DBs with the same DBID as the one you are backing up? Are they connect to the same RMAN catalog?
    Iordan Iotzov
    http://iiotzov.wordpress.com/

  • Problem Login to Weblogic Server and Enterprise Manager Page

    Hi master and guru,
    I have installed WebLogic 10.3.5, SOA 11.1.1.5.0 and OIM 11.1.1.5.0 in production server.
    But when trying to login to Weblogic Server page (http:\\<host>:7001\console), failed without error.
    And when trying to login to Enterprise Manager page (http:\\<host>:7001\em), failed also.
    The error in log :
    initIgnoreList:Register 'oracle_ias_farm' login page url:/em/faces/targetauth/emasLogin
    <Oct 27, 2011 10:04:49 AM ICT> <Warning> <Socket> <BEA-000402> <There are: 5 active sockets, but the maximum number of socket reader threads allowed by the configuration is: 4. You may want to alter your configuration.>
    m_connection-jpss null
    <Oct 27, 2011 10:05:09 AM ICT> <Error> <oracle.iam.platform.emmbeans.OIMDomainClusterMXBeanImpl> <BEA-000000> <Not able to fetch the OIMDB Info. Either the application is undeployed or the application server is shutdown. Hence populating the Information Not Available values for them>
    <Oct 27, 2011 10:05:09 AM ICT> <Error> <oracle.iam.platform.emmbeans.OIMDomainClusterMXBeanImpl> <BEA-000000> <Not able to fetch the SOA Info. Either the application is undeployed or the application server is shutdown. Hence populating the Information Not Available values for them>
    <Oct 27, 2011 10:05:09 AM ICT> <Error> <oracle.iam.platform.emmbeans.OIMDomainClusterMXBeanImpl> <BEA-000000> <Not able to fetch the OVD Info. Either the application is undeployed or the application server is shutdown. Hence populating the Information Not Available values for them>
    <Oct 27, 2011 10:05:09 AM ICT> <Warning> <oracle.iam.platform.emmbeans.OIMDomainClusterMXBeanImpl> <BEA-000000> <Found multiple WLS Domain MBeans>
    <Oct 27, 2011 10:05:14 AM ICT> <Warning> <oracle.adfinternal.view.faces.lifecycle.LifecycleImpl> <BEA-000000> <ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6
    java.lang.IllegalStateException: Cannot forward a response that is already committed
    +     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:122)+
    +     at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch(FacesContextFactoryImpl.java:267)+
    +     at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:469)+
    +     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:140)+
    +     at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)+
    +     at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)+
    +     at oracle.sysman.emSDK.adfext.ctlr.EMViewHandlerImpl.renderView(EMViewHandlerImpl.java:149)+
    +     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:800)+
    +     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:294)+
    +     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:214)+
    +     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)+
    +     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)+
    +     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)+
    +     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)+
    +     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:164)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)+
    +     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)+
    +     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)+
    +     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)+
    +     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)+
    +     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)+
    +     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:105)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)+
    +     at java.security.AccessController.doPrivileged(Native Method)+
    +     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)+
    +     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)+
    +     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)+
    +     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)+
    +     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)+
    +     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)+
    +     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)+
    +     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)+
    +     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)+
    +     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)+
    +     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)+
    >
    <Oct 27, 2011 10:05:14 AM ICT> <Error> <HTTP> <BEA-101020> <[ServletContext@333967374[app:em module:/em path:/em spec-version:2.5]] Servlet failed with Exception
    java.lang.IllegalStateException: Cannot forward a response that is already committed
    +     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:122)+
    +     at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     Truncated. see log file for complete stacktrace+
    >
    <Oct 27, 2011 10:05:14 AM ICT> <Notice> <Diagnostics> <BEA-320068> <Watch 'UncheckedException' with severity 'Notice' on server 'AdminServer' has triggered at Oct 27, 2011 10:05:14 AM ICT. Notification details:
    WatchRuleType: Log
    WatchRule: (SEVERITY = 'Error') AND ((MSGID = 'WL-101020') OR (MSGID = 'WL-101017') OR (MSGID = 'WL-000802') OR (MSGID = 'BEA-101020') OR (MSGID = 'BEA-101017') OR (MSGID = 'BEA-000802'))
    WatchData: DATE = Oct 27, 2011 10:05:14 AM ICT SERVER = AdminServer MESSAGE = [ServletContext@333967374[app:em module:/em path:/em spec-version:2.5]] Servlet failed with Exception
    java.lang.IllegalStateException: Cannot forward a response that is already committed
    +     at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:122)+
    +     at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:410)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidad.context.ExternalContextDecorator.dispatch(ExternalContextDecorator.java:44)+
    +     at org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$OverrideDispatch.dispatch(FacesContextFactoryImpl.java:267)+
    +     at com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:469)+
    +     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:140)+
    +     at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)+
    +     at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)+
    +     at oracle.sysman.emSDK.adfext.ctlr.EMViewHandlerImpl.renderView(EMViewHandlerImpl.java:149)+
    +     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:800)+
    +     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:294)+
    +     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:214)+
    +     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266)+
    +     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)+
    +     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)+
    +     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)+
    +     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:164)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)+
    +     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)+
    +     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)+
    +     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)+
    +     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)+
    +     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)+
    +     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:105)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)+
    +     at java.security.AccessController.doPrivileged(Native Method)+
    +     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)+
    +     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)+
    +     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)+
    +     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)+
    +     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)+
    +     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)+
    +     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)+
    +     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)+
    +     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)+
    +     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)+
    +     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)+
    +     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)+
    +     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)+
    SUBSYSTEM = HTTP USERID = <WLS Kernel> SEVERITY = Error THREAD = [ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' MSGID = BEA-101020 MACHINE = IDM_APP TXID = CONTEXTID = 3ca8d5161a516ac2:7fbc50ed:1334350f599:-8000-0000000000000083 TIMESTAMP = 1319684714138
    WatchAlarmType: AutomaticReset
    WatchAlarmResetPeriod: 30000
    >
    <Oct 27, 2011 10:05:15 AM ICT> <Alert> <Diagnostics> <BEA-320016> <Creating diagnostic image in c:\oracle\middleware\user_projects\domains\base_domain\servers\adminserver\adr\diag\ofm\base_domain\adminserver\incident\incdir_18 with a lockout minute period of 1.>
    But the weird thing is success when login to SOA (http:\\<host>:8001\soa-infra)
    Can anyone help me why this problem occured and how to solve it?
    Thank you,
    Ivan P.

    Hi
    Try to increase socket limits
    Normally you can do this within the admin console , Servers -> Configuration -> Tuning -> Socket Readers
    For you, since you can't login, set the ThreadPoolPercentSocketReaders in the config.xml to a higher value than 5
    kind regards
    Michel

Maybe you are looking for