Insufficient Permission When Creating Standby

I have a remote server which I believe I have prepped appropriately. I have installed grid infrastructure /w ASM, and database software. I have created a virtually blank initMyDB.ora file with a single parameter (db_name) as per docs. I start that skeletal database instance in NOMOUNT mode.
I go to RMAN and try to connect to the primary as SYS. It connects easily.
I try to connect to the local instance as SYS. It gives me the "ora-01031 insufficient privileges" error.
I can, of course, log into +ASM and change the SYS password/change permissions/etc, but I cannot log into the skeletal instance and do anything to SYS as the db is in NOMOUNT mode.
I'm a Data Guard newcomer, so what am I doing wrong? DB is 11r2 and OS is RHEL 5.
Thanks

893968 wrote:
I have a remote server which I believe I have prepped appropriately. I have installed grid infrastructure /w ASM, and database software. I have created a virtually blank initMyDB.ora file with a single parameter (db_name) as per docs. I start that skeletal database instance in NOMOUNT mode.
I go to RMAN and try to connect to the primary as SYS. It connects easily.
I try to connect to the local instance as SYS. It gives me the "ora-01031 insufficient privileges" error.
I can, of course, log into +ASM and change the SYS password/change permissions/etc, but I cannot log into the skeletal instance and do anything to SYS as the db is in NOMOUNT mode.
I'm a Data Guard newcomer, so what am I doing wrong? DB is 11r2 and OS is RHEL 5.
ThanksHi,
In a Data Guard configuration, all physical and snapshot standby databases must use a copy of the password file from the primary database,
and that copy must be refreshed whenever the SYSOPER or SYSDBA privilege is granted or revoked,
and after the password of any user with these privileges is changed.
Regards
Mahir M. Quluzade

Similar Messages

Insufficient privileges when creating MV with alter session set current_sch

I am getting Insufficient privileges when creating MV with alter session set current_schema=Application schema name. User running the alter session is DBA user. If run as SYSDBA, MV is created successfully. DB Version is 10.2.0.3
I observed similiar issue with regular View also in 9.2.0.6 also.
Any advice is greatly appreciated.
Thanks,
Siva

Sounds like your management needs a stern lecture on the concept of change management. <g>
I am not debating what you do. I am questioning the logic, or lack thereof, of doing it that way. My recommendation would be to change your procedure to one that:
A. Is more in line with good change management practices.
B. Works.

Is there shutdown of primary database needed when creating standby by Grid?

I want to create physical standby database
using EM Grid Control. Is there neccessary during
the process to shutdown primary database, e.g.
when creating backup of primary database?
Thanks for advise,
M.

Yes you need to shutdown the database while,
Backup all database files.
After changing the entries in pfile you need to start the database through pfile.
After changing the listener, reload the listener file.

Problem when create standby database

hello,
I have two server(NT4.0,SP6) installed Oracle 8i(8.1.6 Enterprise) at the same directory.I want one as the primary database,another one as the standby database.
The two database have the same SID,use SQL*Plus it can access each other.
My operating steps as below:
1.on primary server:
1)connect internal;
2)shutdown immediate;
3)copy all datafiles(*.DBF) to a backup directory;
4)startup
5)alter database create standby controlfile as 'd:\oracle\ora81\ILLDB\standby.ctl'
6)alter system archive log current
2.on standby server:
1)copy all backuped datafile,standby.ctl,all redo log files from primary server to standby server,overwrite all same name files;
2)modify the init.ora,add this parameter:
"standby_archive_dest = "location=D:\Oracle\oradata\ILLDB\archive" ";
3)statup oracle service in Service control manel;
4)run svrmgrl.exe;
5)startup nomount;
6)alter database mount standby database;
then a error message appear:
"ORA-01665 controlfile is not a standby controlfile".
I don't know which step is mistake.Please tell me correct steps.
Thanks

I did face the similar problem while trying to create and startup a clone database for Point in Time Recovery (PITR). The error message is
ORA-01696 controlfile is not a clone controlfile
Are you folks have any idea how do I resolve this problem?? Is there any way to create clone control file??

Insufficient Privileges when create materialized view as user system

If I login as system (connect sys/****@DevDB) and try to create a materialized view for another schema (e.g. XDCONTROLDB), I get the insufficient privileges error. If I login as sys as sysdba then I can create successfully.
I have searched some ariticles in Google and grant create any snapshot, create any table, create any view, global query rewrite, select any table system privileges to system but still get the same error.
Any other privileges I need to grant to system?
Cheers
below is a sample script to create the view which get the error:
CREATE MATERIALIZED VIEW XDControlDB."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT * From XDControlDB.RiskInstance;
Message was edited by:
user500168
Message was edited by:
user500168

Thanks for your reply. After I grant privileges to system, I login as system and try to create the view as below which I get the insufficient privileges error:
CREATE MATERIALIZED VIEW XDControlDB."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT 1 From XDControlDB.RiskInstance;
As you can see, I try to create the view under a schema called 'XDCONTROLDB'. If I login as sys as sysdba, then it create successfully.
After I create UserA, and grant the privileges I mentioned in the ealier post, I login as UserA, and run the statement above I get the same privileges error. But if I change the stament to below which will create the view under UserA's schema, then it create successfully:
CREATE MATERIALIZED VIEW UserA."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT 1 From XDControlDB.RiskInstance;
Looking for your suggestions,
Cheers

ORA-01031: insufficient privileges when creating a table in other schema

Dear all,
I appreciate your help please in this issue :
when i try to issue the below statement to create a table in an another schema than the user i am connected in
CREATE TABLE SCHEMA_NAME_B.HST_ARCH nologging AS
SELECT *
FROM HST
WHERE 1 = 0;
I always get ORA-01031: insufficient privileges error, even if i have granted the create table privilege to the user i am connected in.
What other privileges should i grant also,
Please if you have any idea.

user562674 wrote:
Dear all,
I appreciate your help please in this issue :
when i try to issue the below statement to create a table in an another schema than the user i am connected in
CREATE TABLE SCHEMA_NAME_B.HST_ARCH nologging AS
SELECT *
FROM HST
WHERE 1 = 0;
I always get ORA-01031: insufficient privileges error, even if i have granted the create table privilege to the user i am connected in.
What other privileges should i grant also,
Can you show us a cut/paste from the sql*plus of session of yours which should show that you have given the privilege directly to this user and after that the command fails?
Aman....

4.0 EA2 - Insufficient Privileges When Creating Object With Proxy

When I have connected by proxying to another user, I receive the following message when trying to create a new object:
The database user has insufficient privileges for the given operation.
Steps to reproduce:
Connect by proxying to another user
Right Click on Views
Select New View
I noticed this under EA1, though, not sure if reported. This worked under 3.2.2

Sounds like your management needs a stern lecture on the concept of change management. <g>
I am not debating what you do. I am questioning the logic, or lack thereof, of doing it that way. My recommendation would be to change your procedure to one that:
A. Is more in line with good change management practices.
B. Works.

Insufficient privileges when creating user logged in as SYS

Hi,
I'm working on 11.1.0.6.0 Enterprise Edition, Advanced Security options, Label Security a and Database Vault installed. (for testing purposes)
I'm creating a new user being logged as SYS using this sentence:
CREATE USER "HR_DIRECTOR" PROFILE "DEFAULT" IDENTIFIED BY "*******" DEFAULT TABLESPACE "USERS" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK;
However, the command fails with the message "Failed to commit: ORA-01031: insufficient privileges . You do not have enough privileges to perform this operation. You must have the appropriate system and object privileges to create, edit, or drop database objects or objects outside of your schema."
Please note that I'm working on a fresh DB install and I have also installed Database Vault in this instance for testing purposes, but still haven't configured any realm or command rules on it.
Is it possible Vault is the reason why I am not able to create a new user?
Thanks and Regards,
Leandro

Hi, It seems I've found it.
After you install Database Vault and associate it with your SID, SYS user is revoked the CREATE USER system privilege.
Only a user with the DV_ACCTMGR role may create, alter or drop a user. This is done in order to separate responsabilities in your database. A SYS user cannot grant himself this role or the DV_OWNER role.
(If interested, check page 10-4 from http://www.oracle.com/pls/db111/to_toc?pathname=server.111/b31222/toc.htm)
Regards,
Leandro

Insufficient priviledge when creating index

upon creating new indexes, using the command :
create index im_art_s_idx_2 on article(cl_story)
indextype is ctxsys.context;
i get the following error :
create index im_art_s_idx_2 on article(cl_story)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE
routine
ORA-20000: interMedia Text error:
ORA-01031: insufficient privileges
ORA-06512: at "CTXSYS.DRUE", line 126
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
ORA-06512: at line 1
I can, however create normal indexes (i.e. by not specifying
the indextype argument). Has anybody got any idea what this
could be about?

grant to user who's gonna create the index CTXAPP
grant ctxapp to xxxx;

Chmod / File permission when creating directory

Hello,
I'm updating an existing website that is developed by someone else.
One of the scripts is used to upload files and is written in JSP (while all other pages are PHP). In this script, a directory is created using following code:
File uploadDir = new File(folder);
if (!uploadDir.exists()) {
uploadDir.mkdir();
This creates a folder with the following arguments: drwxr-xr-x (nummeric: 755).
This means that only the owner has write-permissions... In another script, the same directory must be used to store some more files. This script is written in PHP and can't access the folder to write.
How can I chmod / set permissions so the group can also write (775)? Using the first JSP-script...
Thanks in advance.
Greetz,
l:x
lx(at)lxit.be

There is no way in java to change the umask of mkdir because to do so is platform-specific.
Either have a separate daemon process look for directories and change permissions, change the default umask of the user the script executes as, or drop to a system call with Runtime.getRuntime and execute chmod yourself.
[this post written from a unix perspective: change terminonolgy as appropriate for windows]

ORA-19505: failed to identify file - RMAN in creating standby DR database.

I got this error when creating standby database at remote target server.
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01"
Here is what I did:
1.   started the listener and created corresponding tnsnames entry at remote standyb server
2. startup nomount to the standby database at remote server for an empty instance (instance name dxp1p).
3. All rman backups are in the /backup mount point at primary and the mount point is shared on the remote server as nfs.   So, whatever have in the backup we should be able to see and read from the remote as well.
4. Run the following at primary rman:
sql 'alter system archive log current';
backup current controlfile for standby;
sql 'alter system archive log current';
crosscheck backup;
crosscheck archivelog all;
exit
5.   Start the rman command from primary after connected to the standby server, as the primary DB uses ASM and the standby DB uses file system for the database files:
RUN
SET NEWNAME FOR DATAFILE 1 to '/u01/dxp1p/data/system01.dbf';
SET NEWNAME FOR DATAFILE 2 to '/u01/dxp1p/data/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 3 to '/u01/dxp1p/data/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 4 to '/u01/dxp1p/data/users01.dbf';
SET NEWNAME FOR DATAFILE 5 to '/u01/dxp1p/data/fxtntdata.dbf';
SET NEWNAME FOR DATAFILE 6 to '/u01/dxp1p/data/fxtntindex.dbf';
SET NEWNAME FOR DATAFILE 7 to '/u01/dxp1p/data/mlogs.dbf';
SET NEWNAME FOR DATAFILE 8 to '/u01/dxp1p/data/dts.dbf';
SET NEWNAME FOR DATAFILE 9 to '/u01/dxp1p/data/dxpsoa.dbf';
SET NEWNAME FOR DATAFILE 10 to '/u01/dxp1p/data/expresso_ts.dbf';
SET NEWNAME FOR DATAFILE 11 to '/u01/dxp1p/data/jms_ts.dbf';
SET NEWNAME FOR DATAFILE 12 to '/u01/dxp1p/data/uup_ts.dbf';
SET NEWNAME FOR DATAFILE 13 to '/u01/dxp1p/data/newpage_ts.dbf';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE for standby
nofilenamecheck
dorecover;
========================================================================
But I got this error from the rman log:
contents of Memory Script:
   set until scn 12245784375453;
   restore clone standby controlfile;
executing Memory Script
executing command: SET until clause
Starting restore at 04-DEC-13
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01
channel aux1: ORA-19870: error while restoring backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-01"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_20131204_833310136_464
channel aux1: ORA-19870: error while restoring backup piece /backup/dxp1p/online/DXP1P_20131204_833310136_464
ORA-19505: failed to identify file "/backup/dxp1p/online/DXP1P_20131204_833310136_464"
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
failover to previous backup
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece /backup/dxp1p/online/DXP1P_CF_c-2027711285-20131204-00
channel aux1: ORA-19504: failed to create file "/oracle/product/11g/dbs/u02/dxp1p/control/control02.ctl"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1
ORA-19600: input file is control file (/u01/dxp1p/control/control01.ctl)
ORA-19601: output file is control file (/oracle/product/11g/dbs/u02/dxp1p/control/control02.ctl)
Finished restore at 04-DEC-13
contents of Memory Script:
   sql clone 'alter database mount standby database';
executing Memory Script
sql statement: alter database mount standby database
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/04/2013 19:06:13
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 12/04/2013 19:06:13
RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
ORA-00205: error in identifying control file, check alert log for more info
=========================================
Not sure why, can somebody help?   Appreciated!

I used company regular script to login to standby instance as sys user from primary DB RMAN as oracle OS user and sys DB user.   We normally run this way for years.
Like this:
$ORACLE_HOME/bin/rman target=/ auxiliary 'sys/sys0rapr321!'@dxp1p_s11 CMDFILE=${HOME}/dba/scripts/rman_cr_dr.cmd
rman_cr_dr.cmd:
RUN
SET NEWNAME FOR DATAFILE 1 to '/u01/dxp1p/data/system01.dbf';
SET NEWNAME FOR DATAFILE 2 to '/u01/dxp1p/data/sysaux01.dbf';
SET NEWNAME FOR DATAFILE 3 to '/u01/dxp1p/data/undotbs01.dbf';
SET NEWNAME FOR DATAFILE 4 to '/u01/dxp1p/data/users01.dbf';
SET NEWNAME FOR DATAFILE 5 to '/u01/dxp1p/data/fxtntdata.dbf';
SET NEWNAME FOR DATAFILE 6 to '/u01/dxp1p/data/fxtntindex.dbf';
SET NEWNAME FOR DATAFILE 7 to '/u01/dxp1p/data/mlogs.dbf';
SET NEWNAME FOR DATAFILE 8 to '/u01/dxp1p/data/dts.dbf';
SET NEWNAME FOR DATAFILE 9 to '/u01/dxp1p/data/dxpsoa.dbf';
SET NEWNAME FOR DATAFILE 10 to '/u01/dxp1p/data/expresso_ts.dbf';
SET NEWNAME FOR DATAFILE 11 to '/u01/dxp1p/data/jms_ts.dbf';
SET NEWNAME FOR DATAFILE 12 to '/u01/dxp1p/data/uup_ts.dbf';
SET NEWNAME FOR DATAFILE 13 to '/u01/dxp1p/data/newpage_ts.dbf';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE for standby
nofilenamecheck
dorecover;
exit
==========================
Oinstall is a group.   I am not sure to use oinstall as a user?

Create standby having offline dropped datafile .

Hi,
How to deal with offline dropped datafiles on source when creating standby .
I've 4 node rac, and one tablespace offline and related bigdatafile droped offline (because of corruption).
SQL> select tablespace_name , status from dba_tablespaces order by status ;
TABLESPACE_NAME                STATUS
OLD_TBS                         OFFLINE
SQL> select TS#,STATUS,ENABLED from v$datafile order by status;
       TS# STATUS ENABLED
        16 OFFLINE DISABLED
Its 4 node RAC 10.2.0.3 and ASM .
select name,TS#,STATUS,ENABLED from v$datafile order by status
+DBG1/dbname/datafile/bigfile.279.615031073
Currently I'm doing something like that
rman target /
catalog backuppiece '/oarch/backup/bigfile.279.615031073';
run{
allocate channel ch1 type disk;
SET NEWNAME FOR DATAFILE 16 TO '+DBG1';
restore datafile 16 from tag='TAG20100209T124507';
SWITCH DATAFILE 16;
release channel ch1;
and then after duplicate is end
SQL> alter database datafile 16 offline drop;
SQL> recover automatic standby database;Please advice.
Regards
GregG

Hi GregG,
I think there is no requirement to file the request with Oracle. :-) Please check the below testcase where I tried to simulate the scenario this time by using RMAN.
Primary Database: oraprd
Physical Standby database: oraphy
SYS @ oraprd>select tablespace_name,file_id from dba_data_files;
TABLESPACE_NAME                   FILE_ID
SYSTEM                                  1
SYSAUX                                  2
UNDOTBS1                                3
USERS                                   4
TEST                                    5
SYS @ oraprd>select TS#,file#,STATUS,ENABLED from v$datafile order by status;
       TS#      FILE# STATUS ENABLED
         6          5 OFFLINE DISABLED
         1          2 ONLINE READ WRITE
         2          3 ONLINE READ WRITE
         4          4 ONLINE READ WRITE
         0          1 SYSTEM READ WRITEConfigure catalog (controlfile) to exclude an offline tablespace TEST and perform the full database backup with standby control file
C:\>rman target sys/abc123@oraprd
connected to target database: ORAPRD (DBID=2633932676)
RMAN> configure exclude for tablespace 'TEST';
using target database control file instead of recovery catalog
Tablespace TEST will be excluded from future whole database backups
new RMAN configuration parameters are successfully storedprimary database backup with standby control file
RMAN> run{
2> allocate channel d1 type disk;
3> allocate channel d2 type disk;
4> backup database format 'c:\temp\rman_oraprd_%U.bkp';
5> backup archivelog all format 'c:\temp\rman_arch_%U.bkp';
6> backup current controlfile for standby format 'c:\temp\rman_standby_%U.bkp';
7> }
released channel: ORA_DISK_1
allocated channel: d1
channel d1: SID=9 device type=DISK
allocated channel: d2
channel d2: SID=143 device type=DISK
Starting backup at 15-JUN-12
file 5 is excluded from whole database backup <===
channel d1: starting full datafile backup set
channel d1: specifying datafile(s) in backup set
input datafile file number=00001 name=C:\APP\XYZ\ORADATA\ORAPRD\ORAPRD\DATAFILE\O1_MF_SYSTEM_DATA_D-ORA11PRD_I-2924940358_TS-SYSTEM_FNO-1_07NDBK6A_.DBF
input datafile file number=00003 name=C:\APP\XYZ\ORADATA\ORAPRD\ORAPRD\DATAFILE\O1_MF_UNDOTBS1_DATA_D-ORA11PRD_I-2924940358_TS-UNDOTBS1_FNO-3_0ANDBK7H_.DBF
channel d1: starting piece 1 at 15-JUN-12
channel d2: starting full datafile backup set
channel d2: specifying datafile(s) in backup set
input datafile file number=00002 name=C:\APP\XYZ\ORADATA\ORAPRD\ORAPRD\DATAFILE\O1_MF_SYSAUX_DATA_D-ORA11PRD_I-2924940358_TS-SYSAUX_FNO-2_08NDBK6A_.DBF
input datafile file number=00004 name=C:\APP\XYZ\ORADATA\ORAPRD\ORAPRD\DATAFILE\O1_MF_USERS_DATA_D-ORA11PRD_I-2924940358_TS-USERS_FNO-4_09NDBK6B_.DBF
channel d1: specifying datafile(s) in backup set
including standby control file in backup set
channel d1: starting piece 1 at 15-JUN-12
channel d1: finished piece 1 at 15-JUN-12
piece handle=C:\TEMP\RMAN_STANDBY_0VNDJJR2_1_1.BKP tag=TAG20120615T123858 commen
t=NONE
channel d1: backup set complete, elapsed time: 00:00:03
Finished backup at 15-JUN-12
released channel: d1
released channel: d2
RMAN> exitBuild the physical standby database using RMAN
C:\>rman target sys/abc123@oraprd auxiliary sys/abc123@oraphy
connected to target database: ORAPRD (DBID=2633932676)
connected to auxiliary database: ORAPRD (not mounted)
RMAN>
RMAN> run{
2> allocate auxiliary channel a1 type disk;
3> allocate auxiliary channel a2 type disk;
4> duplicate target database for standby nofilenamecheck;
5> }
using target database control file instead of recovery catalog
allocated channel: a1
channel a1: SID=134 device type=DISK
allocated channel: a2
channel a2: SID=10 device type=DISK
Starting Duplicate Db at 15-JUN-12
contents of Memory Script:
   restore clone standby controlfile;
executing command: SET NEWNAME
Starting restore at 15-JUN-12
file 5 is excluded from whole database backup <==
channel a1: starting datafile backup set restore
channel a1: specifying datafile(s) to restore from backup set
channel a1: restoring datafile 00002 to C:\APP\XYZ\ORADATA\ORAPRD\ORAPHY\DATAFILE\O1_MF_SYSAUX_DATA_D-ORA11PRD_I-2924940358_TS-SYSAUX_FNO-2_08NDBK6A_.DBF
channel a1: restoring datafile 00004 to C:\APP\XYZ\ORADATA\ORAPRD\ORAPHY\DATAFILE\O1_MF_USERS_DATA_D-ORA11PRD_I-2924940358_TS-USERS_FNO-4_09NDBK6B_.DBF
channel a1: reading from backup piece C:\TEMP\RMAN_ORAPRD_0PNDJJN7_1_1.BKP
datafile 3 switched to datafile copy
input datafile copy RECID=10 STAMP=786026596 file name=C:\APP\XYZ\ORADATA\ORAPHY\ORAPHY\DATAFILE\O1_MF_UNDOTBS1_7XPWYO19_.DBF
datafile 4 switched to datafile copy
input datafile copy RECID=11 STAMP=786026596 file name=C:\APP\XYZ\ORADATA\ORAPHY\ORAPHY\DATAFILE\O1_MF_USERS_7XPWYN8N_.DBF
Finished Duplicate Db at 15-JUN-12
released channel: a1
released channel: a2
RMAN>start the managed recovery
SYS @ oraphy>recover managed standby database disconnect;
Media recovery complete.
SYS @ oraphy>select TS#,file#,STATUS,ENABLED from v$datafile order by status;
       TS#      FILE# STATUS ENABLED
         6          5 OFFLINE DISABLED
         1          2 ONLINE READ WRITE
         2          3 ONLINE READ WRITE
         4          4 ONLINE READ WRITE
         0          1 SYSTEM READ WRITE
SYS @ oraphy>select thread#,sequence#,process,status from v$managed_standby;
   THREAD# SEQUENCE# PROCESS   STATUS
         1         24 RFS       IDLE
         1         22 MRP0      WAIT_FOR_GAP <---------------
....archive the current log on the primary database
SYS @ oraprd>select thread#,sequence#,status from v$log;
   THREAD# SEQUENCE# STATUS
         1         22 INACTIVE
         1         23 ACTIVE
         1         24 CURRENT
SYS @ oraprd>alter system archive log current;
System altered.
SYS @ oraphy>select thread#,sequence#,process,status from v$managed_standby;
   THREAD# SEQUENCE# PROCESS   STATUS
         1         25 RFS       IDLE
         1         25 MRP0      WAIT_FOR_LOG <-------- the recovery is in progress on the standby database.
....Regards,
Vaibhav

Creating standby database using RMAN

When I'm creating standby database with RMAN command
'duplicate for standby' backups for creating standby database
have to be accessible from host where standby database
is created. I can copy the backups to standby host, or use
NFS to share the disk with backups to standby host.
But when I have backups in ASM diskgroup how can
I achieve it would be accessible from standby host?
Thanks a lot for advice,
M.

OK, thanks,
I will create standby using Grid, but I have the following problem:
database instance is running on the host where I want
to create standby database. The running instance is for
testing purposes and has the same db_name, db_unique_name, db_domain
parameters as in primary database.
I will change db_unique_name to be distinct from primary database one,
should I also change instance SID not to be the same in
testing database and standby on the same host, or when creating standby
database I can specify distinct one for standby database?

"insufficient RAM to fill" message when creating panoramas - 16 GB on my computer?[was: RAM]

Why am I getting "insufficient RAM to fill" message when creating panoramas when I have 16 GB on my computer?

You don't say which version of PSE or which operating system, but except for PSE 12/mac, all versions of PSE are 32 bit programs, which means they can only use a maximum of about 3 GB of ram, no matter how much you have in your system. You can try going to the editor>preferences>performance and upping the percentage available for PSE.

Error - when creating a standby database with EM 10g Grid Control

Hi,
I am experiencing some problems when I want to create through the EM 10g Grid Control a standby database from a allready existing db. At step 2 when the files should be generated and copied to the other system, I am always getting the error that there isn't enough disk space on the other system. This can't be because there is at least 30GB free and the installer is asking for less than 1GB. I was searching the whole internet for a solution to this issue, but there was just nothing that could help me out with that point...
Has someone an idea at this point? Thanks for helping...
I am working on a Windows 2003 Server - Enterprise Edition for every system (Grid Control, Primary DB and Standby DB).
Best regards,
Patrick.

Check that filesystem space using GC under targets>hosts on which you are trying to create standby. Do you have any specific error message from GC ? If GC shows proper size under host filesystem section then there shuld be no such problem. Double chk ur locations too.
Regards,
http://askyogesh.com

Insufficient Permission When Creating Standby

Similar Messages

Maybe you are looking for