TUNING RMAN NLS PARAMETERS
Hi allduring the restoration of the database to the point in time we must choose the NLS_LANG and NLS_DATE_FORMAT settings, is it mandatory parameters are... ?
My restore of database to the point in time is not successful. There just restore. Please let me know these parameters...
Thank you!
Setting NLS Environment Variables
Before calling RMAN, set NLS_DATE_FORMAT and NLS_LANG environment variables. These variables determine format used for the time parameters in the RMAN commands including restore, recover and report.
The following example shows the typical language and date format settings:
NLS_LANG = American
NLS_DATE_FORMAT =' Mon ' JJ YYYY HH24:MI:SS
Specification of Dates in the RMAN commands
When you specify the dates of RMAN commands, the date string can be either:
A literal string whose format is the setting NLS_DATE_FORMAT.
Expression SQL type DATE, for example, ' SYSDATE-10 "or" TO_DATE (January 30, 1997 ',' DD/MM/YYYY ') ".". " Note that the second example includes its own date format mask and therefore regardless of the current setting NLS_DATE_FORMAT.
Some examples of typical date parameters in the RMAN commands:
ARCHIVELOG backup time ' SYSDATE-31' until ' SYSDATE-14';
restore the database up to the time "TO_DATE('12/20/98','MM/DD/YY')";
Specify the database character set
If you are going to use RMAN to connect to a database that is not mounted, and then mount the database later, RMAN is always connected, set the NLS_LANG variable so that it also specifies the character set used by the database.
A database that is not mounted assumes the default character set, which is US7ASCII. If your character set is different from the default, then RMAN returns errors after the installation of the database. To avoid this problem, set the NLS_LANG to specify the character set of the target database. For example, if the character set is WE8DEC, you can set the parameter NLS_LANG as follows:
NLS_LANG = AMERICAN_AMERICA.we8dec.
--------------------------------------------------------------------------------
Note:
You must set the NLS_LANG and NLS_DATE_FORMAT for NLS_DATE_FORMAT to use.
This is the excerpt from the following link:
http://docs.Oracle.com/CD/A84870_01/doc/server.816/a76990/preparer.htm
What is the exact error that you have found?
Tags: Database
Similar Questions
-
NLS parameters in a connection pool environment
I have limited experience of localization/globalization and I am building an application, using Oracle APEX 4.2/Oracle 11 g db, which takes care of several users of different nationalities. I have a specific question, but first... can anyone recommend good books, blogs and websites to learn more about best practices for the many things you need to think in this area?
Second, my precise question is... Since my application will use a connection pool, how it works as far as setting the NLS parameters for a given client session? In the typical client/server architecture that I know that you would simply change the NLS parameter when the user connects, and this change would govern just the session of this user database. It's a different approach when we are in an environment of connection pool? If this is not the case, how Oracle now manages the parameters of the client session this session of customer may engage in more than one session of db in its lifetime?
You can set the runtime: http://docs.oracle.com/cd/E16655_01/appdev.121/e17961/global_primary_lang.htm#HTMDB14002
Thank you
Sergiusz
-
For the other sessions to find the NLS parameters.
Hi all
Database server Environment Details: 2 Node Oracle 10.2.0.4 RAC on Solaris Operating SystemParameter in Spfile: nls_sort = BINARY_CI nls_comp = LINGUISTIC nls_language = AMERICANParameters in database: SQL> select * from nls_database_parameters; PARAMETER VALUE ------------------------------ ------------------------------------------------------------ NLS_LANGUAGE AMERICAN NLS_NCHAR_CHARACTERSET AL16UTF16 NLS_TERRITORY AMERICA NLS_CURRENCY $ NLS_ISO_CURRENCY AMERICA NLS_NUMERIC_CHARACTERS ., NLS_CHARACTERSET AL32UTF8 NLS_CALENDAR GREGORIAN NLS_DATE_FORMAT DD-MON-RR NLS_DATE_LANGUAGE AMERICAN NLS_SORT BINARY NLS_TIME_FORMAT HH.MI.SSXFF AM NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR NLS_DUAL_CURRENCY $ NLS_COMP BINARY NLS_LENGTH_SEMANTICS BYTE NLS_NCHAR_CONV_EXCP FALSE NLS_RDBMS_VERSION 10.2.0.4.0 20 rows selected.
Now, each index on columns of type of data characters in this database are created as function of the Index of base to support Case Insensitive search using nls_sort to BINARY_CI, as shown below.Parameters at client's environment variable(Its Application sever on Windows): Oracle Client 10.2.0.4 nls_sort = BINARY_CI nls_comp = LINGUISTIC
What worries me started when I created by mistake an index btree normal on a character column. After this error just by curiosity, I enabled index followed up on this clue, when I checked in v$ object_usage it got USED!CREATE UNIQUE INDEX UX_NAME_BR ON ONS (NLSSORT("NAME",'nls_sort=''BINARY_CI'''),"TYPE_ID", "UNIT_NUMBER", "DOMICILE", "IS_ACTIVE", "ID")
So I strongly suspect that there are a few sessions connected to this database with different values of NLS instead of nls_sort = BINARY and nls_comp = LINGUISTIC...
Sort of, I did a little test in production to confirm this, as shown below:
IDX_COD index is a regular btree index...PARAMETER VALUE -------------------------------------------------- ------------------------------------------------------------ NLS_LANGUAGE AMERICAN NLS_TERRITORY AMERICA NLS_CURRENCY $ NLS_ISO_CURRENCY AMERICA NLS_NUMERIC_CHARACTERS ., NLS_CALENDAR GREGORIAN NLS_DATE_FORMAT DD-MON-RR NLS_DATE_LANGUAGE AMERICAN NLS_SORT BINARY NLS_TIME_FORMAT HH.MI.SSXFF AM NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR NLS_DUAL_CURRENCY $ NLS_COMP BINARY NLS_LENGTH_SEMANTICS CHAR NLS_NCHAR_CONV_EXCP FALSE 17 rows selected. SQL> set autotrace traceonly exp SQL> select id,is_active from ons where domicile = 'US' and id = 440 and name = 'AMERICAN COMPANY'; Execution Plan ---------------------------------------------------------- Plan hash value: 1171456783 --------------------------------------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop | --------------------------------------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1 | 49 | 4 (0)| 00:00:01 | | | | 1 | PARTITION RANGE ALL | | 1 | 49 | 4 (0)| 00:00:01 | 1 | 3 | |* 2 | TABLE ACCESS BY LOCAL INDEX ROWID| ONS | 1 | 49 | 4 (0)| 00:00:01 | 1 | 3 | |* 3 | INDEX RANGE SCAN | IDX_COD | 1 | | 4 (0)| 00:00:01 | 1 | 3 | --------------------------------------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - filter("ID"=440) 3 - access("DOMICILE"='US' AND "NAME"='AMERICAN COMPANY') SQL> alter session set nls_sort=BINARY_CI; Session altered. SQL> alter session set nls_comp=LINGUISTIC; Session altered. SQL> select * from nls_session_parameters; PARAMETER VALUE -------------------------------------------------- ------------------------------------------------------------ NLS_LANGUAGE AMERICAN NLS_TERRITORY AMERICA NLS_CURRENCY $ NLS_ISO_CURRENCY AMERICA NLS_NUMERIC_CHARACTERS ., NLS_CALENDAR GREGORIAN NLS_DATE_FORMAT DD-MON-RR NLS_DATE_LANGUAGE AMERICAN NLS_SORT BINARY_CI NLS_TIME_FORMAT HH.MI.SSXFF AM NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR NLS_DUAL_CURRENCY $ NLS_COMP LINGUISTIC NLS_LENGTH_SEMANTICS CHAR NLS_NCHAR_CONV_EXCP FALSE 17 rows selected. SQL> select id,is_active from ons where domicile = 'US' and id = 440 and name = 'AMERICAN COMPANY'; Execution Plan ---------------------------------------------------------- Plan hash value: 270874147 ------------------------------------------------------------------------------------------------------------------------------ | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop | ------------------------------------------------------------------------------------------------------------------------------ | 0 | SELECT STATEMENT | | 1 | 49 | 2 (0)| 00:00:01 | | | | 1 | TABLE ACCESS BY GLOBAL INDEX ROWID| ONS | 1 | 49 | 2 (0)| 00:00:01 | ROWID | ROWID | |* 2 | INDEX RANGE SCAN | UX_NAME_BR | 1 | | 2 (0)| 00:00:01 | | | ------------------------------------------------------------------------------------------------------------------------------ Predicate Information (identified by operation id): --------------------------------------------------- 2 - access(NLSSORT("NAME",'nls_sort=''BINARY_CI''')=HEXTORAW('669696E6720636F6D70 616E7900') AND "ID"=440) filter("ID"=440 AND NLSSORT(INTERNAL_FUNCTION("DOMICILE"),'nls_sort=''BINARY_CI ''')=HEXTORAW('7588700') )
So, how can I find which sessions have access to these indexes and find the session parameters nls level connected to this database.
I know there is no way to find settings nls for the other sessions without tracing it...
Kickbacks will not work me
NLS_DATABASE_PARAMETERS
NLS_SESSION_PARAMETERS
Could someone help me please to find these sessions these sessions that are not level session as BINARY_CI and LANGUAGE settingsTrigger may fail if the storage space for the trace table is full. This trigger does not use dynamic SQL code: in this perspective, it is a bit more secure.
I don't know any other way supported to retrieve another session NLS parameters. But he can there have no documented similar to this one http://dioncho.wordpress.com/2009/07/18/spying-on-the-other-session/.
-
Download weekdaynum, independent of the nls parameters.
What is the best way to get Weekdaynum for a date?
The algorithm must be independent of the nls parameters.
This solution depends on nls_teritory and works differently when
nls_territory = "AMERICA."
and when it is ESTONIA:
select decode ( to_char(sysdate,'DY','nls_date_language=english'), 'MON', 1, 'TUE', 2, 'WED', 3, 'THU', 4, 'FRI', 5, 'SAT', 6, 'SUN', 7 ) WeekdayNum from dual;Something like this should also work, it just takes mod 7 the Julian date and add the value 1.
with data as (select sysdate + rownum - 1 as dt from dual connect by rownum < 10) select dt, decode(mod(to_char(dt,'J'),7) + 1, '1', 'Monday', '2', 'Tuesday', '3', 'Wednesday', '4', 'Thursday', '5', 'Friday', '6', 'Saturday', 'Sunday') as result from data; -
NLS parameters in stored procedure
Hello
I've struggled for some time with the release of one of my SPs
It goes like this:
Begin
Declare the cursor as a query
loop and write lines in a file
end
It is, I can't seem to be able to set the NLS settings correctly. I need the dates out as YYYY-MM-DD HH24:MI:SS, but it doesn't seem to work at all. The columns are the DATE data type, but no matter what I do (of course I do something wrong!) I'm not able to get output only HH24:MI:SS AAAA-MM-JJ.
I tried to use TO_DATE DBMS_SESSION in the query, the immediate execution of the ALTER SESSION SET NLS_DATE.... SET_NLS. Nothing seems to work, any help is appreciated (maybe I lost the DMBS_SESSION.) SET_NLS or something?).
Example code:
Thanks in advance,CREATE OR REPLACE PROCEDURE TEST (parameters.. ) AS /*variables*/ BEGIN DECLARE CURSOR c_AICTT IS SELECT TO_DATE(DATE1,'YYYY-MM-DD HH24:MI:SS'), DATE2 FROM DATES; . . .
NACEURLooks like what you want is not TO_DATE, TO_CHAR.
Don't change the NLS settings; they "belong" to the customer, not to your code.
To_char will make an explicit conversion, the NLS settings does not come into play.
-
PHP, Oracle Package and NLS parameters.
Dear all,
with this environment:
Oracle Database 11g 11.2.0.3.0 64 bit Production
PHP version: 5.3.3
Oci8 Version 2.0.7
I have a website in Php language that runs:
ALTER SESSION SET NLS_DATE_FORMAT = ''YYYY/MM/DD HH24:MI:SS"
when loading the first page;
then it executes package Oracle (ZZZJOB):
$ORA_DB = oci_pconnect(ORA_USER, ORA_PASSWORD, ORA_TNSCATALOG, "UTF8"); --$sql="BEGIN ZZZJOB.RUN_ZZZTEST_JOB; END"; $stid = oci_parse($ORA_DB, html_entity_decode($sql)); $r = oci_execute($stid, OCI_DEFAULT);
Then, once the parcel has been returned, the new default nls_date_format in the web pages of Php (running other queries) is the default value of database, i.e. HH24:MI:SS MON-DD-YYYY
How can I prevent the execution of (all) change of package the nls format used by Php?
It seems that the previous connection Php / session is replaced by the "Oracle Package / login»
Thank you
Igor
Finally, I found the solution: if I write:
DBMS_SCHEDULER.run_job ('ZZZTEST_JOB', TRUE); --the defaultthe NLS settings are changed; Instead, with
DBMS_SCHEDULER.run_job ('ZZZTEST_JOB', FALSE);any necessary changes are made.
Thank you
Igor
-
Day of week (1-7) and the NLS parameters
It's embarrassing, but I'm going nuts here.
Today is Monday. Here, it's the first day of the week.
Thus,.
Very well, it's probably because of my NLS settings:SQL> select to_char(sysdate, 'd') from dual; TO_CHAR(SYSDATE,'D') -------------------- 2 1 row selected.
We will change then, in something where people know that Monday is the first day of the week ;)SQL> select * from nls_session_parameters where parameter = 'NLS_DATE_LANGUAGE'; PARAMETER VALUE ------------------------------ ---------------------------------------- NLS_DATE_LANGUAGE AMERICAN 1 row selected.
No luck, how about youSQL> alter session set nls_language = german; Session altered. SQL> select to_char(sysdate, 'd') from dual; TO_CHAR(SYSDATE,'D') -------------------- 2 1 row selected.
May be variable, bad. How about NLS_TERRITORYSQL> select to_char(sysdate, 'd', 'NLS_DATE_LANGUAGE = danish') from dual; TO_CHAR(SYSDATE,'D','NLS_DATE_LANGUAGE=DANISH') ----------------------------------------------- 2 1 row selected.
Great! - But I do not alter session, statement andSQL> alter session set nls_territory = 'DENMARK'; Session altered. SQL> select to_char(sysdate, 'd') from dual; TO_CHAR(SYSDATE,'D') -------------------- 1 1 row selected.
Dang, out of ideas. I'm just on a mission impossible here?SQL> select to_char(sysdate, 'd', 'NLS_TERRITORY = denmark') from dual: select to_char(sysdate, 'd', 'NLS_TERRITORY = denmark') from dual * Error at line 1 ORA-12702: invalid NLS parameter string used in SQL function
Concerning
Peter
BANNER ---------------------------------------------------------------- Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64biHi, Peter,.
What is the problem?
You want just an expression which, given a date, will return an integer (1 for Monday,..., 7 for Sunday), independent of the NLS settings?
If so:1 + TRUNC (dt) - TRUNC (dt, 'IW') -
Problem with the archive log when you use RMAN for backup and restore (11g 2)
Hello world
Please help me solve this problem.
I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
-First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}
D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}Repeat 7 times (Monday-> Saturday). And I got these files:
[oracle@rac ~]$ ls -l /u01/backup/
total 400280
-rw-r----- 1 oracle oinstall 10158080 Jan 20 07:23 c-1428943247-20160120-01
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:04 c-1428943247-20160120-02
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:05 c-1428943247-20160120-03
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:06 c-1428943247-20160120-04
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:08 c-1428943247-20160120-05
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:08 c-1428943247-20160120-06
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:09 c-1428943247-20160120-07
-rw-r----- 1 oracle oinstall 10158080 Jan 20 08:32 c-1428943247-20160120-08
-rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
-rw-r----- 1 oracle oinstall 2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
-rw-r----- 1 oracle oinstall 4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
-rw-r----- 1 oracle oinstall 11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
-rw-r----- 1 oracle oinstall 146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
-rw-r----- 1 oracle oinstall 884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
-rw-r----- 1 oracle oinstall 82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
-rw-r----- 1 oracle oinstall 294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
-rw-r----- 1 oracle oinstall 18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
-rw-r----- 1 oracle oinstall 155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
-rw-r----- 1 oracle oinstall 131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
-rw-r----- 1 oracle oinstall 647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
-rw-r----- 1 oracle oinstall 8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
-rw-r----- 1 oracle oinstall 2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
-rw-r----- 1 oracle oinstall 1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
-rw-r----- 1 oracle oinstall 1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
-rw-r----- 1 oracle oinstall 327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1And
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
80 B 0 A DISK 20-JAN-16 1 1 YES DB_FULL
81 B 0 A DISK 20-JAN-16 1 1 YES DB_FULL
82 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_FULL
83 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_FULL
84 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_FULL
85 B F A DISK 20-JAN-16 1 1 NO TAG20160120T072332
86 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
87 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
88 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
89 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080440
90 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
91 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
92 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
93 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080545
94 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
95 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
96 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
97 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080657
98 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
99 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
100 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
101 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080801
102 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
103 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
104 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INC
105 B F A DISK 20-JAN-16 1 1 NO TAG20160120T080844
106 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
107 B 1 A DISK 20-JAN-16 1 1 YES DB_INC
108 B A A DISK 20-JAN-16 1 1 YES ARCL_BKP_INCMy configuration of rman:
RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u01/backup/backup_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default- Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
Starting restore at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
channel ORA_DISK_2: skipped, AUTOBACKUP already found
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 20-JAN-16
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
released channel: ORA_DISK_2
RMAN> restore database;
Starting restore at 20-JAN-16
Starting implicit crosscheck backup at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=18 device type=DISK
Crosschecked 29 objects
Finished implicit crosscheck backup at 20-JAN-16
Starting implicit crosscheck copy at 20-JAN-16
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 20-JAN-16
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
using channel ORA_DISK_2
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 20-JAN-16-Fourth, the problem here, I got the database;
.. .every oky until this line...starting media recoverychannel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=15
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/20/2016 08:50:22RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841
The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
82 2.16M DISK 00:00:00 20-JAN-16
BP Key: 82 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL
Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1
List of Archived Logs in backup set 82
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 1 1154833 20-JAN-16 1177422 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
83 3.88M DISK 00:00:00 20-JAN-16
BP Key: 83 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL
Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1
List of Archived Logs in backup set 83
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 1 1162729 20-JAN-16 1188784 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
84 10.68M DISK 00:00:01 20-JAN-16
BP Key: 84 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_FULL
Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1
List of Archived Logs in backup set 84
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 2 1177422 20-JAN-16 1201833 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
88 1.81M DISK 00:00:01 20-JAN-16
BP Key: 88 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1
List of Archived Logs in backup set 88
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 3 1201833 20-JAN-16 1204844 20-JAN-16
1 4 1204844 20-JAN-16 1204893 20-JAN-16
1 5 1204893 20-JAN-16 1204958 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
92 143.00K DISK 00:00:00 20-JAN-16
BP Key: 92 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1
List of Archived Logs in backup set 92
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 6 1204958 20-JAN-16 1205034 20-JAN-16
1 7 1205034 20-JAN-16 1205253 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
96 80.00K DISK 00:00:00 20-JAN-16
BP Key: 96 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1
List of Archived Logs in backup set 96
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 8 1205253 20-JAN-16 1205354 20-JAN-16
1 9 1205354 20-JAN-16 1205433 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
100 18.00K DISK 00:00:00 20-JAN-16
BP Key: 100 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1
List of Archived Logs in backup set 100
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 10 1205433 20-JAN-16 1205519 20-JAN-16
1 11 1205519 20-JAN-16 1205559 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
104 128.00K DISK 00:00:00 20-JAN-16
BP Key: 104 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1
List of Archived Logs in backup set 104
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 12 1205559 20-JAN-16 1205624 20-JAN-16
1 13 1205624 20-JAN-16 1205739 20-JAN-16
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
108 8.00K DISK 00:00:00 20-JAN-16
BP Key: 108 Status: AVAILABLE Compressed: YES Tag: ARCL_BKP_INC
Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1
List of Archived Logs in backup set 108
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 14 1205739 20-JAN-16 1205796 20-JAN-16
1 15 1205796 20-JAN-16 1205840 20-JAN-16
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.Sorry for a long post.> 1 and from the 1205841 SNA sequence
The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).
The message
channel ORA_DISK_1: restoring archives Journal
Archives journal thread = 1 sequence = 15
channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading
channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC
indicates that he has restored the sequence up to 15
You can check the log file alert database instance for messages on the fact of recovery.
He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.
Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve. An uncomitted transaction is cancelled.
Hemant K Collette
-
10g | RMAN | Daily backups in case files
Hi guys
RMAN > show all.
using the control file of the target instead of recovery catalog database
RMAN configuration parameters are:
CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK to 'D:\oracle\rman\backup\%F ';
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE the FORMAT of DISC TYPE CHANNEL DEVICE "D:\oracle\rman\backup\%U";
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFSCT. ORA'; # by default
RMAN >
The foregoing describes RMAN configuration, I've done with the installation of 10g in my laptop for learning purposes. Now, how can I make sure that every day the backup is created in case files as below mentioned few
D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_21
D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_22
D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_23
D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_24
My backups used to get created under individual records until I changed the type of RMAN channel with "CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\oracle\rman\backup\%U';' "
Please suggest.
Thanks in advance
rthampi wrote:
Hi guys
RMAN > show all.
using the control file of the target instead of recovery catalog database
RMAN configuration parameters are:
CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK to 'D:\oracle\rman\backup\%F ';
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE the FORMAT of DISC TYPE CHANNEL DEVICE "D:\oracle\rman\backup\%U";
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFSCT. ORA'; # by default
RMAN >
The foregoing describes RMAN configuration, I've done with the installation of 10g in my laptop for learning purposes. Now, how can I make sure that every day the backup is created in case files as below mentioned few
D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_21
D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_22
D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_23
D:\oracle\product\10.2.0\flash_recovery_area\SCT\BACKUPSET\2015_11_24
My backups to be created under individual records until I changed the type of RMAN channel with ' CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\oracle\rman\backup\%U ';
Please suggest.
Thanks in advance
These 'individual files' report to the FRA. What you need to do is allow rman use the FIU, which it wants to do by default. Then clear your default settings trying to name/place your backups differently.
-
During a planned migration, which method of database migration is the best? Data Pump or RMAN?
I ask this because I recently had to migrate a database to a new feature of ODA and our application developer head was upset because I used pump data to the database to the new platform and it took a few post import scripts to set permissions to what they were before the move. He suggests to use RMAN, because it will restore the database to exactly how it was previously without having to restore the permissions. I would like to know what methods are you using and which one is better?
Thanks in advance ^_^
He suggests using RMAN
Yes, absolutely, and not just for the reason you mention: don't have time to stop a problem for you? Re: Tuning RMAN - active database in double with size 1.7 to
-
See date + hour in the date cells without changing the NLS settings
We have a lot of columns date containing the date + time values, I often need to see while browsing the data in the table.
Settings for the date format default NLS are exact to 'Russia', our database uses the default, which is then used by SQLDeveloper. For example, to display the values of time, I should write or select to_char manually with appropriate or the NLS under "Database" settings in preferences. Of course, it seems preferable to modify the NLS parameter.
However, the date format change NLS has certain side effects. For example, it affects various tasks involving mainly exporters, which are launched from SQLDeveloper, because the to_char default to values date format also changes. Of course we could blame the lazy developers does not explicitly specify the formats, but it does not change the fact that the results of the task execution are 'bad', and which can be quite difficult to notice until the following tasks fail. Also, if I'm not mistaken, NLS_DATE_FORMAT also affects to_date default format, making import text and date columns questioning pretty boring. It's better safe than sorry, so I need to keep the NLS parameters
So, is it possible to set date format only for the display of the values in the data grid, without affecting the NLS settings somehow? I'm fine with just about anything, including writing an extension myself if necessary, I just need to work. If it is not possible, SQL Developer Team please add this parameter, or at least display a tooltip on mouseover, displaying the value of the cell "full"?
NLS is the only way to affect the display of dates in the grids. To_char formatting is up to you good - he will use that you define in the function call.
-
RMAN - Backed Up n times the sentence does not
Hello
We use the following script to backup our database every night complete.
It is supposed to keep the archiving on disk logs are not backed up 3 times. However, when I run the script it deletes a journal archive newly created immediately after the backup is performed.
Also, when I ask RMAN > backup archivelog sequence list XXXX; We see only one copy.
I use the same script on a different database without any problem.
= Environment database =.
3 node RAC (backup works on 1 node)
Oracle 11.2.0.4 on OEL 5.10
= RMAN for backup script =.
run
{
' SQL ' alter the entire system "_backup_disk_bufcnt" = 64 scope = memory;
' SQL ' alter the entire system "_backup_disk_bufsz" = 1048576 scope = memory;
allocate channels ch1 device type disk format ' / u02/PEBS/apps_st/backup1/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch2 device type disk format ' / u02/PEBS/apps_st/backup2/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channels ch3 device type disk format ' / u02/PEBS/apps_st/backup1/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch4 device type disc format ' / u02/PEBS/apps_st/backup2/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch5 device type disk format ' / u02/PEBS/apps_st/backup1/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch6 device type disc format ' / u02/PEBS/apps_st/backup2/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch7 device type disc format ' / u02/PEBS/apps_st/backup1/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch8 device type disc format ' / u02/PEBS/apps_st/backup2/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch9 device type disc format ' / u02/PEBS/apps_st/backup1/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch10 device type disc format ' / u02/PEBS/apps_st/backup2/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch11 device type disc format ' / u02/PEBS/apps_st/backup1/201402061512/PEBSFULL_%d-%I-%T-%U';
allocate channel ch12 device type disc format ' / u02/PEBS/apps_st/backup2/201402061512/PEBSFULL_%d-%I-%T-%U';
under compressed backupset level incremental backup 0 article size 16g tag database 'DB_TAGE_201402061512 ';
ARCHIVELOG backup all missed 3 times.
output channel ch1.
output channel ch2.
output channel ch3;
output channel ch4;
output channel ch5.
output channel ch6;
output channel ch7.
output channel ch8.
output channel ch9.
output channel ch10.
output channel ch11.
output channel ch12;
}
= To delete RMAN script & backup Controlfile/Spfile =.
run
{
assign the channel c1 type disc format ' / u02/PEBS/apps_st/backup1/201402061512/%d-%I-%T-%U';
delete noprompt archivelog all backed up 3 times on the TYPE of DEVICE drive;
remove obsolete redundancy noprompt = 3;
Save the spfile tag = "SP_TAGE_201402061512";
backup current controlfile tag = "CT_TAGE_201402061512";
output channel c1;
}
= Configuration of RMAN =.
RMAN > show all.
Database with db_unique_name PEBS RMAN configuration parameters are:
CONFIGURE REDUNDANCY 1 RETENTION STRATEGY;
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 5 TYPE OF BACKUP BACKUPSET.
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO 12488 M;
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u02/PEBS/apps_st/backup1/ctrl_auto_bck/snapcf_PEBS.f';
Hello
It sounds like the BUG 16692232 - EXPECT RMAN BACKUP ARCHIVELOG ALL NOT SUSTAINABLE to REMOVE ALL ENTRY DOESNOT WORK AS set out in paragraph 12.1
I suggest you to increase Service demand and to obtain confirmation on the same.
Thank you
Renu
-
Hot RMAN backup fails every time in R12.
Hi experts,
Please suggest me that I have to plan rman backup hot. I have "write" command to perform hot backup. When I take backup hot of 1st time the backup completed successfully. but when I run the same command resume backup for the second day. it is impossible to give space issue I havhot e calendar for daily use rman backup.
I had to take the backup hot daily and I want backup overwrite the backup file according to the daily backup.
Please suggest me what I need to make changes in the configuration of rman and the rman command.
OS - réhèl 5.6
Database - 11.1
EBS - r12.3
configuration of RMAN:
RMAN > show all.
Database with db_unique_name UAT RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
CONFIGURE BACKUP OPTIMIZATION
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / d06/UAT/rman_hot_backup/Backup_daily%d_DB_%u_%s_%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BZIP2 '; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / d06/UAT/db/tech_st/11.1.0/dbs/snapcf_UAT.f'; # by default
RMAN >##############################################################################################################
RMAN command that I used to make hot extra strength 0 cumulative backup.
RMAN > run
{
allocate channels c1 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
allocate channel c2 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
allocate channels c3 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
allocate channel c4 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
cumulative incremental database backup level 1 more archivelog;
output channel c1;
output channel c2.
output channel c3.
output channel c4.
}If something bad in the configuration of rman and my order please suggest me to take the backup hot every day with success.
concerning
pritesh Rodriguez
Hi Pritesh, thanks for the update. You can mark this thread as answered if your questions have been answered. cordially Karan
-
You cannot change the format of RMAN backup
Hello!
I am trying to restore a backup of the database controlfiles in a new host solaris11 with RMAN in oracle 10 g. I have a solaris10 box where I installed database10g. As far as I know what I have to do is this:
> define the dbid = 718308982;
> startup nomount;
> set controlfile autobackup format of disc type of the device of ' / u01/app/oradata/ACBET/%F';
> Restore controlfile autobackup.
However when I try to change the format, nothing happens.
RMAN > set controlfile autobackup format of disc type of the device of ' / u01/app/oradata/ACBET/%F';
executing command: SET CONTROLFILE AUTOBACKUP FORMAT
RMAN > show all.
RMAN configuration parameters are:
CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP # by default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # default < = same configuration by default...
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
And when I try to do the restore command I get the following error:
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 1626 devtype = DISK
field of recovery destination: / u01/app/oradata/ACBET/backup
name of database (or unique name of database) used for research: ACBET
channel ORA_DISK_1: no record not found in the recovery area
channel ORA_DISK_1: looking for autobackup day: 20131115
channel ORA_DISK_1: looking for autobackup day: 20131114
channel ORA_DISK_1: looking for autobackup day: 20131113
channel ORA_DISK_1: looking for autobackup day: 20131112
channel ORA_DISK_1: looking for autobackup day: 20131111
channel ORA_DISK_1: looking for autobackup day: 20131110
channel ORA_DISK_1: looking for autobackup day: 20131109
channel ORA_DISK_1: found no autobackup in 7 days
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the restore command at 11/15/2013 10:50:22
RMAN-06172: no autobackup couldn't find or handle specified is not a valid copy or a piece
It seems he's looking for in the right path of recovery of the area, but I don't know why it's a failure.
Thank you in advance,
Nock
Hello world
The problem with this restoration has been far from my knowledge. The real problem was that the backup files that they sent were made in a different boutien than the one I used in the new host. For the sake of those who find this post in the future, you can not use rman to make. Until the date of this post, he must either use a simple import/export (with pump data if you like) or using transportable tablespaces to move a database between the hosts with another platform.
Thanks for all the help.
Nock
-
Why RMAN is not storage of backups in "db_recovery_file_dest?
Hello
Select the name, the value of the parameter $ v
WHERE name = 'db_recovery_file_dest.
NAME VALUE db_recovery_file_dest /ora_backup When I run the following commands, RMAN lance store backups in "$ORACLE_HOME/dbs':
RMAN > check effective additional 0 logical backup
format "% d_ %%U t_ level0_.
as a database of compressed backupset;
My understanding is that RMAN should save the backups under '/ora_backup'.
And when I run the following command, RMAN stores save under ' / ora_backup ':
RMAN > backup database;
Could you get it someone please let me know what I'm missing here?
Here is the config RMAN:
RMAN > show all.
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 10 TYPE OF BACKUP BACKUPSET.
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 5 G;
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE the SNAPSHOT CONTROLFILE NAME to "/app/oracle/product/10.2.0/dbee/dbs/snapcf_< SID >.f '; # by default
RMAN >
Best regards
If you specify a FORMAT, it substitutes for the use of the FRA.
Run a
INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE BACKUP
Hemant K Collette
Maybe you are looking for
-
Satellite Pro U200-10I - need of detailed specifications
Hello guys,. I have the laptop mentioned above and I want to know the specification of this laptop. I tried the Toshiba Web site but I failed.
-
delivery of calendar iPhoto Luxembourg
Hello When I buy a calendar (which I did several times) is will not ship to my country (Luxembourg) by default. It will only be available in Belgium. In the past I have already ordered and received my calendars, but never without significant delay, a
-
I use LabView 8.5 Pro with IVI Compliance Package 4.3. I'm trying to simulate a DMM using class IVI drivers. I get the following message: Error 1074130425 has occurred to be initialized with Options.vi IviDmm, Possible reasons: The primary error: (He
-
Hello I remember Matt and/or users in trying to impregnation said brand would be able to downgrade 2.1 to 1.5 once the upgrade has been officially released. The upgrade was released, well, honestly, I would go back to 1.5. Anyone know where I can fin
-
Send by server communication error
Until today I could wireless transfer my photos from my HS SX280 on my computer from a remote location using 'send via the server '. Today, after the first file download progress bar is completed, I get "Communication error" "Error detected". Is some