Creating physical standby through Cloud Control 12C fails

Hi,
I have a SR with MOS on physical standby setup through Cloud Control 12C. My setup is two Exadata Quarter RAC X2-2 installations and i'm setting up primary standby/between those two installations. Lets call them exa1db01(primary) and exa2db01(standby).
I'm using Cloud version 12.1.0.2 and agents on the latest version and patch. We just upgraded before Christmas. When i try to create a physical standby it fails on the transfer stage with below error:
"Uncaught exception in command fileTransfer: unable to instantive value javax.xml.bind.JAXBE1ement@46dd1e39 for attribute actualException"
At the moment its sent to developement so i have to wait for a fix. The reason for posting here is that i cant believe that this is not working on Cloud Control 12.1.0.2. This is basic functionality and i'm amazed that this is a bug. Our Exadata installation is running on 11.2.0.3 BP10 so it should be fairly fresh.
I truly believe the problems needs to be somewhere in our installation or the connectivity between our Exadata environments. Do any of you have any experience with DG through Cloud on that participial version ?
Cheers

Hello again;
Check the solution in this: ( and note the multiple versions of oracle it covers )
UNABLE TO FIND GRID INFRASTRUCTURE LISTENER (Doc ID 1483234.1)
Best Regards
mseberg

Similar Messages

Creating Standby database using Cloud Control 12C

Hi,
I want to setup Standby database for my existing RAC database, Both standby and PRimary databases are on 11.2.0.3 and we are using "Cloud Control 12C".
After specifing and testing the Host creddential and Database credentials and choosing the Backup method when I click next I get following error message
"Username- The Specified user must own the source database oracle server installation."
I am giving the host credential as oracle, we use single os user "Oracle" for all our installation and administration.
This is AIX OS and 11.2.0.3 database installation.
Any help will be appreciated.
Regards
Bhushan

Guys,
After searching for 2 days on web and raising question on OTN, in the last we resolved the issue. The issue was registering the primary database with correct oracle binaries.
We have 2 set of binaries Oracle Infrastructure and Oracle RDBMS, The database was register in 12C with Oracle Infrastructure binaries. I changed that and every thing is working soomth.
regards
bhushan

Create physical standby failed at destination preparation step

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

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

Problem in identifying control file when creating physical standby

hi there,
(database version: 10.2.0.4
plateform linux)
I'm using the command as below to create physical standby database from backup:
rman target / auxiliary sys/tiger@paceview
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Sep 4 18:05:53 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PACEVIEW (DBID=2092349485)
connected to auxiliary database: PACEVIEW (not mounted)
run {
allocate auxiliary channel c1 device type DISK;
set until sequence 38;
duplicate target database for standby dorecover nofilenamecheck;
released channel: ORA_DISK_1
allocated channel: c1
channel c1: sid=35 devtype=DISK
allocated channel: c2
channel c2: sid=36 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 04-SEP-12
contents of Memory Script:
   set until scn 138180211934;
   restore clone standby controlfile;
   sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 04-SEP-12
channel c1: restoring control file
ORA-19625: error identifying file /backup/rman/paceview/DEL1_standby.ctl
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file (/backup/rman/paceview/DEL1_standby.ctl)
ORA-19601: output file is control file (/PGHProdDB/oradata/paceview/control1.ctl)
failover to previous backup
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/04/2012 18:01:44
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restorei have already tried crosscheck but still giving same error
thanks

Hello;
So this is what I would do :
Backup Primary ( change to your directory as need )
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
}Move the backup and duplicate like this :
rman target sys/password@PRIMARY auxiliary /
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
}For complete details of this method see :
http://www.visi.com/~mseberg/duprman2.html
Best Regards
mseberg

Error while creating physical standby database using Oracle Grid 10.2.0.5

Hi All,
I am setting up data guard using oracle grid.
Primary database version: - 10.2.0.4
Standby database version: - 10.2.0.4
Primary OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
Standby OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
I am creating physical standby database using EM. But it is getting failed with error message in sqlnet.ora file
Fatal NI connect error 12533, connecting to:
(DESCRIPTION=(ADDRESS_LIST=)(CONNECT_DATA=(SERVICE_NAME=INPRDSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=indb50.oii.com)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 10.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
Time: 17-AUG-2010 02:40:07
Tracing not turned on.
Tns error struct:
    ns main err code: 12533
    TNS-12533: TNS:illegal ADDRESS parameters
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0As we can see, address_list is empty.
Can anyone suggest what could be the reason behind this?

Dear user13295317,
Here is the error explanation;
Oracle Error :: TNS-12533
TNS:illegal ADDRESS parameters
Cause
An illegal set of protocol adapter parameters was specified.
In some cases, this error is returned when a connection cannot be made to the protocol transport.
Action
Verify that the destination can be reached using the specified protocol.
Check the parameters within the ADDRESS section of TNSNAMES.ORA.
Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform.
Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.Hope That Helps.
Ogan

Creating physical standby databases with DG Broker & OEM

Hi guys,
I manage 8i, 9i & 10g databases through OEM 10.2.0.2.
Today, I would like to create physical standby db for the most important applications. Because I'm a lazy guy, I'd like to do it the easiest way, with GUI and wizzards provided by OEM.
1. Do you know any tutorial on the Internet that would help to do it easily ? My only source up to now is the official DB broker documentation (http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/toc.htm), which is 300 pages long like every Oracle doc. I'd appreciate any tutorial that could lead me straight to the essential. I've heard that is not so tricky to create a physical standby db
2. Is the procedure really different to create (and then manage) a physical standby database on Oracle 8i, 9i and 10g ? Is it possible to do it through DB Broker and OEM for every version ?
thank you for your help
Antoine

Antionio,
Oracle Documentation is the best source of configuring any Oracle component.
But, If you do not want to read the entire doc, and want to configure Dataguard Broker (without OEM), then here is the Link.
http://www.oracledba.org/10g/dr/10gR2_dataguard_RAC_to_RAC.html#Configure_Dataguard_Broker:

Oracle VM and Oracle VM Template for Enterprise Manager Cloud Control 12c M

Hello!
After installation of *"Oracle VM 3.1.1 Media Pack v1 for x86_64 (64 bit)"* to bare hardware
can I install Oracle VM Template for Enterprise Manager Cloud Control 12c Media Pack ?
Is it the wrong plan ?
What to do if I need to set VLAN №1 ? (according note of installer I have to choose number between 2 and 4094 )
Thanks and regards,
Pavel
Edited by: Pavel on Jul 30, 2012 5:01 AM

Yes, you can install Oracle VM Manager, create a server pool with the one parent Oracle VM server in it, and then deploy the Oracle VM template in the pool. Once EM VM is up and running, you can register the same Oracle VM Manager with EM, to manage the pool.
In general, it is not recommended that you use the OVM server backend directly. But for bootstrapping the EM environment, you can also try the following:
Download the OVM Template on the Oracle VM server. From the OVM server terminal itself you can do "xm create" to spin a new virtual machine using the Oracle VM teamplate. Once the VM comes up, VNC into the VM and configure the EM OMS and agent.

Oracle VM Template for Enterprise Manager Cloud Control 12c Media Pack v1

Hello
I download Oracle VM Template for Enterprise Manager Cloud Control 12c Media Pack v1
I was checking the structure and I found this
[oracle@em12c bin]$ cd /u01
[oracle@em12c u01]$ ls
app lost+found OracleHomes oracle-template.sh scripts
[oracle@em12c u01]$ cd OracleHomes/
[oracle@em12c OracleHomes]$ ls
checkpoints db11g Middleware
[oracle@em12c OracleHomes]$ pwd
/u01/OracleHomes
[oracle@em12c OracleHomes]$ cd db11g/
[oracle@em12c db11g]$ ls
admin cfgtoollogs checkpoints diag fast_recovery_area oradata product
[oracle@em12c db11g]$ cd ..
[oracle@em12c OracleHomes]$ cd Middleware/
[oracle@em12c Middleware]$ ls
[oracle@em12c Middleware]$
The Database has all binaries but Middleware is empty
Same body knows about this issue.
Regards

Yes, you can install Oracle VM Manager, create a server pool with the one parent Oracle VM server in it, and then deploy the Oracle VM template in the pool. Once EM VM is up and running, you can register the same Oracle VM Manager with EM, to manage the pool.
In general, it is not recommended that you use the OVM server backend directly. But for bootstrapping the EM environment, you can also try the following:
Download the OVM Template on the Oracle VM server. From the OVM server terminal itself you can do "xm create" to spin a new virtual machine using the Oracle VM teamplate. Once the VM comes up, VNC into the VM and configure the EM OMS and agent.

Dbcontrol migrate to enterprise manager cloud control 12c

Currently we are using Oracle 11gR2 database in our enterprise and manage them with EM database control.
We're planning to migrate to centralized management with oracle enterprise manager cloud control 12c.
Is it possible to manage DBs both ways, with db control AND using EMCC agent simultaneously?
Is there a easy way to migrate db control managed DBs to be managed by agent?
I've searched EM documentation but didn't find any topic about this job.

Hi P2
Yes You can manage DB from both. But why you are going to use EM instead of Cloud Control 12. You Can do each and every work from it more tan EM. Cloud Control 12c is very good tool.
No. But You can easily setup them using manual agent push or auto discovery method from cloud control 12c. You need to create password less ssh login to both side for oracle user and open the relevant ports from network. It is very easy. After add agent you can add targets from relevant hosts easily.
Thanks
Dilshan
Edited by: user11923797 on Dec 24, 2012 10:39 AM

Acknowledge multiple incidents on OEM cloud control 12c

Hey Guys,
Is there a way to acknowledge multiple incidents through the OEM cloud control 12c GUI like we had in OEM 10g and 11g? I cannot find an option to select multiple incidents and this is really bugging me a lot.
Thanks
Abhishek

From the oracle link you gave
"Select the incidents to which you want to respond. You can select multiple incidents by holding down the Control key and selecting individual incidents or you can hold down the Shift key and select the first and last incidents to select a contiguous block of incidents."
Thanks Mani! Fist thing I'll try tomorrow morning
Doesn't work for me Mani... Anyone else facing issues?
Message was edited by: oracle.dba.89

Notification email from Cloud Control 12c

I configured email notification in Cloud Control 12c for database down and tablespace full and other errors. But I don't see email sent to me. I am not sure which step I missed. Here is what I did:
set up notification method
set up metrix template and applied this template to database instances and listeners.
created a incident rule and subscribe it to the dba.
But when database is down, I don't see email sent to me. What's wrong here?
S.

Never mind. I figured i out and made it work.

Cloud Control 12c identifies unused Weblogic version on Managed Server

I'm using Cloud Control to monitor our domain. In this case I upgraded from WebLogic 10.3.1 to Weblogic 12.1.2.0.0 by installing 12c on a separate Oracle/Middleware/Oracle_Home and updateing the startup script to use this new WL_Home location.
The Weblogic 10.3.1 installation is still there.
When I connect through Cloud Control to discover the Middleware Targets (WebLogic) it identifies my server as being 10.3.1
I checked the path and classpath in the startup script and there are no references to the 10.3 path. How is the cloud control agent finding the inactive one ?
any help is appreciated

For the error messagee:
Shell path is incorrect or not defined.:/usr/local/bin/bash(SH_PATH),-c(SH_ARGS) on host XXX. Check the property values in the following files in this order, ssPaths_<plat>.properties or sPaths.properties or Paths.properties, in "/oracle/em12c/oms/oui/prov/resources" directory.For more details, refer to the Oracle Enterprise Manager Basic Installation Guide.
yes , you are suppose to change the shell patch as its at a different location.
The file where you have to chnage is: $<OMS_HOME>/oui/prov/resources/hpi.properties and change the variable: SH_PATH=
Try the agent deployment
On your another question: deploy manual agent , you have to get the em12c agent binaries usings elf update console. For information on Self Update and how you can use it to download the software, see the chapter on Self Update in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
http://docs.oracle.com/cd/E24628_01/doc.121/e24473/self_update.htm#CACBHCBH

Cloud Control 12c: Configuration Details Error

Hi,
I'm currently in the process of installing the Oracle Enterprise Manager Cloud Control 12c, after typing the configuration details (step 5 of 8), I get an error popup window stating the following:
The following prerequisite check failed because the ORacle Database, where the Management Repository will be configured, does not meet the configuration requirements. Fix the issue manually base on the recommendation offered for this prerequisite, and click OK. For more details check the logs: /oraInventory/logs/emdbprereqs
Prereq Name:
Check the compatible instance prarameter value.
Recommendation:
The compatible instance parameter must be set to the same version value as the database instance of the EM repository.
When I check the repos_perf.log, I see the following fails:
Executing Prereq Action
executing Action: select count(*) from v$log where 300000000 > bytes
output: 3
Prerequisite failed
Running component repos_perf Done
Executing component :repos_perf
Running component repos_perf Done
How can I set parameter?
Thanks,
Olivares

Hi Olivares,
Assuming your question is about setting the compatible initialization parameter, you can connect to the repository database (e.g. using sqlplus as user system or sys) to execute the following command, then restart the database:
ALTER SYSTEM SET COMPATIBLE = <value> SCOPE=SPFILE;
EX:
ALTER SYSTEM SET COMPATIBLE = '11.2.0.0.0' SCOPE=SPFILE;
If necessary, see the following doc for guidance on the parameter value:
http://docs.oracle.com/cd/E24628_01/install.121/e22624/appdx_about_emprereqkit.htm#CIHHBGFD
Regards,
- Loc

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

How to integrate OPS 12c with EM cloud control 12c

As title. We checked the documents of OPS 12c and didn't find a way to integrate OPS 12c enterprise controller with EM cloud control 12c.
Is it ready now? Where can we download a separate opar for OMS? Any official documents we can reference?
Regards,
Yu Wang

There's a ton of things in OC that you can't do in OEM, at least not that I know of. Such as:
OVM Server for Sparc (LDOM) management
S10/S11 zone management
patching Solaris
updating Solaris 11
provisioning Solaris (9, 10, 11)
ABE management
firmware provisioning
If you are an all-Linux shop then you may have an argument but Solaris wise I don't think OEM scratches the surface of OC.
At an even higher level, OEM is more geared for the App layer while OC is more geared for the OS/system/virtualization layer.
My $.02.

Creating physical standby through Cloud Control 12C fails

Similar Messages

Maybe you are looking for