Registering Cloned AS Instance Into Grid Control Fails With java.sql.SQLException: ORA-20245, Does Not Exist ORA-06512 at "SYSMAN.EM_TARGET"
(Doc ID 861976.1)
Last updated on JUNE 07, 2023
Applies to:
Enterprise Manager for Fusion Middleware - Version 10.1.2.0.2 and laterOracle Fusion Middleware - Version 10.1.2.0.2 and later
Enterprise Manager Base Platform - Version 12.1.0.1.0 and later
Information in this document applies to any platform.
Symptoms
- An Oracle Application Server (AS 10g) instance has been cloned from one server to another. It is not clear if all cloning steps from Administrator's Guide have been followed correctly and/or any issues remained unresolved.
- Each AS instance can be accessed/administered from its own AS Console, and it shows the correct instance name on top of the ASConsole Home page.i.e.
The source server name: web1.eg.oracle.com
The source instance Name: app1.web1.eg.oracle.com
and:
The destination server name (Cloned): web2.eg.oracle.com
The destination instance Name (Cloned): app2.web2.eg.oracle.com - When attempting to register the newly cloned instance to a Grid Control (10.2+) via the Grid Control Console, it fails with the following error messages in the Grid Control Console "Discovery" page:
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |