Bug 12725963 - New database connection fails with ORA-12541 after vip failover
| Bug 12725963 - New database connection fails with ORA-12541 after vip failover [ID 12725963.8] | |||||
|
| |||||
| 修改時間 07-SEP-2011 型別 PATCH 狀態 PUBLISHED | |||||
Bug 12725963 New database connection fails with ORA-12541 after vip failover
This note gives a brief overview of bug 12725963.The content was last updated on: 07-SEP-2011
Click here for details of each of the sections below.
Affects:
Product (Component) Oracle Server (PCW) Range of versions believed to be affected Versions BELOW 12.1 Versions confirmed as being affected Platforms affected Generic (all / most platforms affected)
Fixed:
This issue is fixed in
Symptoms: |
Related To: |
Description
In a clusterware configuration, if 2nd network is used and an additional vip and listener is created on it, ORA-12541 could be raised after the vip fails over. ORA-12541 is raised when connecting to database via 2nd vip and listener. Rediscovery Notes: If you see ORA-12541 after vip fail over and additional vip is used, you might hit this issue.WorkaroundNone
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/756652/viewspace-712046/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- XDMCP connection failsAI
- Bug 13250486 : ADD STANDBY DATABASE FOR TARGET WITH FLASHBACK ON FAILS WITH ERRDatabaseAI
- Recreating Controlfile With New Database Name Fails ORA-01503_ 109502.1DatabaseAI
- SQLPLUS Fails With SP2-1503 SP2-0152 After New 11.2 Installation解決SQLAI
- Performing a Failover to a Physical Standby DatabaseORMAIDatabase
- How to configure Client Failover after Data Guard Switchover or Failover [ID 316740.1]clientAI
- Performing a Switchover to a Physical Standby Database and failoverORMDatabaseAI
- After failed upgrade, startup fails on ORA-00704 [ID 1345417.1]AI
- OGG Connection test fails with: weblogic.transaction.internal.TimedOutException:AIWebException
- ORA-16649: possible failover to another database prevents this database from beiAIDatabase
- Vip Does Not Failover When Nodeapps Stopped (Doc ID 749160.1)AIAPP
- How to Restore the Database Using AMDU after Diskgroup CorruptionRESTDatabase
- Recover physical standby database after loss of archive log(2)DatabaseHive
- lightdb WARNING: could not establish connection after 30000 ms
- 【故障處理】Bug : ASM FAILS WITH CHECKRESOURCE ERROR ERROR CODE = 139ASMAIError
- Recover Database Fails with RMAN-06558 [ID 1185074.1]DatabaseAI
- 【oracle官網】 Restoring a Database on a New HostOracleRESTDatabase
- Oracle Database 12C New FeatureOracleDatabase
- Duplicating a Database Without Recovery Catalog or Target ConnectionDatabase
- 請高手指點A connection to the database could not be madeDatabase
- Recover database after disk loss (Doc ID 230829.1)Database
- Recover physical standby database after loss of archive log – roll forward(轉)DatabaseHiveForward
- 【rac故障】root.sh報錯Unable to get VIP info for new node
- OMS Startup Fails during Repository Connection Attempt due to_310772.1AI
- 1 Oracle Database Release 20c New FeaturesOracleDatabase
- Flashback New Features and Enhancements in Oracle Database 10gOracleDatabase
- ConnectionManager.getConnection() failed to obtain a connection after 11 retries. The exception fromAIException
- oracle create a new database using backup controlfile to traceOracleDatabase
- Oracle10g New Feature -- 4. Flashback DatabaseOracleDatabase
- Database Startup Fails with ORA-01113, ORA-01110DatabaseAI
- Oracle Database Fails to Start with Error ORA-12547 [ID 1307075.1]OracleDatabaseAIError
- CDH5之Unexpected error.Unable to verify database connectionH5ErrorDatabase
- can close the database Connection before the JTA transaction commit or rollDatabaseMIT
- Enabling Database Resident Connection PoolingDatabaseIDE
- Unable To Open Database After ASM Upgrade From Release 11.1 To Release 11.2DatabaseASM
- iOS Xcode, 解決“Could not insert new outlet connection”的問題。iOSXCode
- Database link 明文密碼bug 更正了Database密碼
- 1 Oracle Database 11g Release 2 (11.2.0.4) New FeaturesOracleDatabase